AI agents call list_post_suggestions 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 or queries data (post suggestions/drafts) from the Posterly service. It has no side effects, creates no data, executes no code, deletes nothing, and involves no financial transactions. It is purely informational retrieval, fitting the Read category.
From the tool's definition Tool name contains 'list' and description states it 'List[s] proactive post suggestions' and 'weekly drafts posterly writes' — retrieves existing suggestions/drafts without modifying them.
Attacks that exploit this kind of access
List proactive post suggestions: evidence-based weekly drafts posterly writes in each account. 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 list_post_suggestions: 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.
list_post_suggestions 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 list_post_suggestions 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 list_post_suggestions. 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.
list_post_suggestions 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 →