Return pending or ignored replies for a Threads post.
AI agents call get_pending_replies to retrieve information from Threads MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about replies to a Threads post. It queries existing data without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—an attacker could enumerate replies to posts but cannot modify, delete, or damage data or systems. This is a straightforward read operation.
From the tool's definition The tool name 'get_pending_replies' and description 'Return pending or ignored replies for a Threads post' indicate a retrieval/query operation with no side effects. The verb 'get' and 'return' explicitly denote data reading.
Attacks that exploit this kind of access
Return pending or ignored replies for a Threads post. It is categorised as a Read tool in the Threads MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Threads MCP Server MCP server in PolicyLayer and add a rule for get_pending_replies: 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 Threads MCP Server. Nothing to install.
get_pending_replies 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_pending_replies 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_pending_replies. 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_pending_replies is provided by the Threads MCP Server MCP server (poisonstefani-dev/threads-mcp). 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 →