Ask Posterly Support AI an authenticated question using Posterly docs plus read-only account/post diagnostics for the caller workspace. Requires POSTERLY_API_KEY with accounts:read and posts:read scopes. Human ticket creation requires request_human=true and confirm_escalation=true after explicit ...
AI agents call ask_support 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 information for support purposes without creating, modifying, deleting, executing code, or moving money. It is fundamentally a Read operation that queries diagnostic data and documentation to answer user questions. The authentication requirements and confirmation flags further limit risk by preventing unintended actions.
From the tool's definition Tool uses 'read-only account/post diagnostics' and requires 'accounts:read and posts:read scopes'. The description explicitly states it reads data from Posterly docs and account/post information without modifying anything.
Attacks that exploit this kind of access
Ask Posterly Support AI an authenticated question using Posterly docs plus read-only account/post diagnostics for the caller workspace. Requires POSTERLY_API_KEY with accounts:read and posts:read scopes. Human ticket creation requires request_human=true and confirm_escalation=true after explicit user confirmation. 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 ask_support: 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.
ask_support 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 ask_support 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 ask_support. 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.
ask_support 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 →