Governed ability
Get post meta
aafm/get-post-meta Read only
Read a single allowlisted meta value from a post the agent can edit (scalar 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 meta 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 meta 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.
Show me the value of the subtitle meta field on post 142.
What is the featured_blurb custom field set to for the launch page?
Read the review_score meta on post 88 for me.
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 meta.
Can this change a meta value?
No, it only reads. Writing is the separate update-post-meta ability, and both stay off until an administrator enables them.
Which fields can it read?
Only keys on the site's allowlist, and only scalar values. Protected and underscore-prefixed keys are excluded.
Does it work on any post?
Only posts the agent's WordPress user can already edit, and every read is written to the audit log.
Governed by default, from the first call.
Get post meta 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.