Governed ability
Get post
aafm/get-post Read only
Retrieve a single post by ID. Returns id, title, status, type, slug, link, author {id, display_name}, dates, full content (rendered HTML by default, or raw markup via content_format; omitted for password-protected posts), excerpt, terms grouped by taxonomy, featured_image {id, url, alt} or null, and meta (allowlisted scalar values only).
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Get post ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Reads only
It reads data and returns it to your client. Nothing on your site is created, changed, or removed.
- Capability gated
A connection only sees Get post if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys but never the values.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
Get post 142 with its full rendered content.
Show me the raw markup and terms for post 88.
Pull up post 305 including its featured image.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Get post.
What happens with password-protected posts?
The content is omitted for password-protected posts, while the remaining fields still return.
Rendered or raw?
Rendered HTML by default, or raw block markup via content_format.
Governed by default, from the first call.
Get post is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.