AI agents use save-draft to create or update resources in AutoWP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoWP MCP Server environment.
The tool creates or modifies post draft data, which is characteristic of Write category operations. Severity is medium because drafts are recoverable and unpublished, limiting immediate blast radius compared to published content. However, it could be misused to create unwanted draft content at scale.
From the tool's definition Tool name 'save-draft' and description 'Save a post draft locally' indicates creation/modification of draft content without publishing. This is a reversible write operation on WordPress post data.
Documented attack patterns abuse exactly the kind of access save-draft gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoWP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for save-draft:
{
"version": "1",
"default": "deny",
"tools": {
"save-draft": {
"limits": [
{
"counter": "save-draft_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save-draft stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save a post draft locally. It is categorised as a Write tool in the AutoWP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoWP MCP Server MCP server in PolicyLayer and add a rule for save-draft: 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 AutoWP MCP Server. Nothing to install.
save-draft 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 save-draft 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 save-draft. 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.
save-draft is provided by the AutoWP MCP Server MCP server (njengah/autowpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoWP MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 AutoWP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.