Return the current Threads publishing quota information for the authenticated account.
AI agents call get_publishing_limit 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 queries and returns quota/limit information about the authenticated account's publishing capabilities. It performs a read-only retrieval of metadata with no ability to modify, delete, execute code, or impact financial systems. The blast radius of misuse is minimal—an attacker could only learn the user's publishing limits, which is informational only.
From the tool's definition Tool name 'get_publishing_limit' and description 'Return the current Threads publishing quota information' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Return the current Threads publishing quota information for the authenticated account. 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_publishing_limit: 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_publishing_limit 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_publishing_limit 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_publishing_limit. 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_publishing_limit 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 →