Approve or ignore a pending Threads reply.
AI agents use manage_pending_reply to create or update resources in Threads MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Threads MCP Server environment.
This tool performs a write operation by changing the moderation state of content. It is reversible (can be undone by changing the approval state again) and does not permanently delete data or commit financial transactions, so it falls under Write rather than Destructive or Financial.
From the tool's definition Tool description states 'Approve or ignore a pending Threads reply' — this modifies the state of a reply by changing it from pending to approved or ignored, which is a reversible state change.
Attacks that exploit this kind of access
Approve or ignore a pending Threads reply. It is categorised as a Write tool in the Threads MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Threads MCP Server MCP server in PolicyLayer and add a rule for manage_pending_reply: 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.
manage_pending_reply is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_pending_reply 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 manage_pending_reply. 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.
manage_pending_reply 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 →