posts_create
AI agents use posts_create to create or update resources in Mcp Esa Server Python — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Esa Server Python environment.
This tool creates new articles/posts in the esa.io documentation system. Creation of data is a Write operation—it modifies state reversibly (created posts can be updated or deleted via sibling tools). It is not Execute (does not run arbitrary code), Destructive (reversible), Financial (no money involved), or Read (has side effects).
From the tool's definition Tool name is 'posts_create' and sibling tools include 'posts_delete', 'posts_get_detail', 'posts_get_list', 'posts_update', confirming this is part of a CRUD suite for articles.
Attacks that exploit this kind of access
posts_create. It is categorised as a Write tool in the Mcp Esa Server Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Esa Server Python MCP server in PolicyLayer and add a rule for posts_create: 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 Esa Server Python. Nothing to install.
posts_create 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 posts_create 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 posts_create. 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.
posts_create is provided by the Mcp Esa Server Python MCP server (scnsh/mcp-esa-server-python). 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 →