AI agents use wp_set_sticky to create or update resources in Claudaborative Editing — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudaborative Editing environment.
This action creates or modifies data reversibly. The tool changes a post's sticky status, which is a metadata property that can be toggled on or off. While it affects site appearance and visibility, it does not delete data, execute arbitrary code, or transfer funds.
From the tool's definition Tool description states 'Pin or unpin the post on the front page' — this modifies post metadata (sticky status) which affects visibility and ordering on the site's front page.
Documented attack patterns abuse exactly the kind of access wp_set_sticky gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claudaborative Editing, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_set_sticky:
{
"version": "1",
"default": "deny",
"tools": {
"wp_set_sticky": {
"limits": [
{
"counter": "wp_set_sticky_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wp_set_sticky 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.
Pin or unpin the post on the front page. It is categorised as a Write tool in the Claudaborative Editing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claudaborative Editing MCP server in PolicyLayer and add a rule for wp_set_sticky: 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 Claudaborative Editing. Nothing to install.
wp_set_sticky 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 wp_set_sticky 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 wp_set_sticky. 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.
wp_set_sticky is provided by the Claudaborative Editing MCP server (pento/claudaborative-editing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claudaborative Editing, 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.
32 Claudaborative Editing tools catalogued and risk-classified — across an index of 43,000+ MCP servers.