AI agents use site_update 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 and potentially sensitive authentication data. While not destructive (changes are reversible) or financial, updating site credentials or settings represents a Write operation with high severity due to the potential impact on site security and configuration integrity. An AI agent misusing this could alter authentication, change site configuration, or compromise access controls.
From the tool's definition Tool name 'site_update' combined with description 'Update site credentials or settings' indicates modification of data. The term 'credentials' is particularly significant as it suggests authentication information management.
Documented attack patterns abuse exactly the kind of access site_update 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_update:
{
"version": "1",
"default": "deny",
"tools": {
"site_update": {
"limits": [
{
"counter": "site_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}site_update 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.
Update site credentials or settings. 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_update: 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_update 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_update 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_update. 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_update 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.