Governed ability
Get page
aafm/get-page Read only
Retrieve a single page 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 pages), 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 page 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 page 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.
Pull up page 12 with its full content.
Show me the raw markup for the homepage.
Get the About page and its featured image details.
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 page.
What happens with password-protected pages?
The content is omitted for password-protected pages, though the other fields still return.
Can I choose rendered or raw markup?
Yes, content comes back as rendered HTML by default, or as raw block markup via content_format.
Governed by default, from the first call.
Get page 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.