AI agents use add to create or update resources in Astro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Astro environment.
The tool is part of an Astro development server alongside retrieval and query tools. The name 'add' indicates creation or modification of Astro project resources (likely routes, integrations, configuration, or similar). Without a description, confidence is reduced, but the naming pattern and context suggest reversible data modification rather than irreversible deletion or code execution.
From the tool's definition Tool name is 'add' in the context of an Astro project development server. Combined with sibling tools that perform read operations (get-*, list-*, search-*), the name 'add' strongly suggests a write operation that creates or modifies project configuration or…
Documented attack patterns abuse exactly the kind of access add gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Astro, and nothing reaches the server without passing your rules. This is the rule we recommend for add:
{
"version": "1",
"default": "deny",
"tools": {
"add": {
"limits": [
{
"counter": "add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add 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.
add. It is categorised as a Write tool in the Astro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Astro MCP server in PolicyLayer and add a rule for add: 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 Astro. Nothing to install.
add 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 add 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 add. 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.
add is provided by the Astro MCP server (astro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Astro, 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.
8 Astro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.