post_schedule_post
AI agents use post_schedule_post to create or update resources in Mcp Metricool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Metricool environment.
This tool creates and schedules social media posts, which is a reversible write operation. While posts can be unscheduled or deleted, the act of scheduling modifies state in the social media management system. Severity is medium because misuse could result in unauthorized posts to public social accounts, but financial loss or permanent data destruction is unlikely.
From the tool's definition Tool name 'post_schedule_post' indicates creation/scheduling of social media content. Server description confirms 'scheduling posts' capability.
Attacks that exploit this kind of access
post_schedule_post. It is categorised as a Write tool in the Mcp Metricool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Metricool MCP server in PolicyLayer and add a rule for post_schedule_post: 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 Mcp Metricool. Nothing to install.
post_schedule_post 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 post_schedule_post 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 post_schedule_post. 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.
post_schedule_post is provided by the Mcp Metricool MCP server (namdzmaso02/mcp-metricool). 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 →