AI agents call get_post to retrieve information from Posterly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing post information by ID and returns its properties. It performs no creation, modification, deletion, or execution of external operations. It is a simple data retrieval operation with no side effects, fitting the Read category. The severity is low because misuse would only expose existing post information, not cause harmful actions or data loss.
From the tool's definition Tool name is 'get_post' and description states it 'Get details of a specific post by ID' and 'Returns caption, status, scheduled time, media, and platform info.' The verb 'Get' and the function of retrieving and returning post details with no modification or…
Attacks that exploit this kind of access
Get details of a specific post by ID. Returns caption, status, scheduled time, media, and platform info. It is categorised as a Read tool in the Posterly MCP Server, which means it retrieves data without modifying state.
Register the Posterly MCP server in PolicyLayer and add a rule for get_post: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Posterly. Nothing to install.
get_post is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_post rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_post. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_post is provided by the Posterly MCP server (posterly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →