AI agents use mixpost_add_post_to_queue to create or update resources in Mixpost — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mixpost environment.
This tool creates a new entry in a queue and modifies queue state, which is a reversible write operation. It does not delete data (hence not Destructive), does not execute arbitrary code (hence not Execute), and does not move money (hence not Financial).
From the tool's definition Tool description states 'Add a post to the publishing queue', which involves modifying the queue state by adding content that will be published to social media platforms. The verb 'add' indicates a create/modify operation.
Attacks that exploit this kind of access
Add a post to the publishing queue. It is categorised as a Write tool in the Mixpost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mixpost MCP server in PolicyLayer and add a rule for mixpost_add_post_to_queue: 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 Mixpost. Nothing to install.
mixpost_add_post_to_queue 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 mixpost_add_post_to_queue 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 mixpost_add_post_to_queue. 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.
mixpost_add_post_to_queue is provided by the Mixpost MCP server (pfarag/mixpost-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 →