Set a site as the default (used when site_id is omitted).
AI agents use site_set_default to create or update resources in WP Astro MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WP Astro MCP environment.
This tool modifies configuration state by setting a default site preference. While not creating or deleting actual content, it changes application settings that control which site subsequent operations target. This is a reversible modification (Write category) rather than a read-only operation.
From the tool's definition The tool description states 'Set a site as the default (used when site_id is omitted)' - this modifies a configuration state that will affect subsequent tool behavior and data context. The tool creates or modifies stored application state.
Documented attack patterns abuse exactly the kind of access site_set_default gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WP Astro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for site_set_default:
{
"version": "1",
"default": "deny",
"tools": {
"site_set_default": {
"limits": [
{
"counter": "site_set_default_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}site_set_default 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.
Set a site as the default (used when site_id is omitted). It is categorised as a Write tool in the WP Astro MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WP Astro MCP server in PolicyLayer and add a rule for site_set_default: 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 WP Astro MCP. Nothing to install.
site_set_default 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 site_set_default 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 site_set_default. 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.
site_set_default is provided by the WP Astro MCP server (vapvarun/wp-astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WP Astro MCP, 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.
60 WP Astro MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.