Create or update a named stage in an agent
AI agents use upsert_stage to create or update resources in BotUyo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BotUyo MCP Server environment.
The 'upsert' pattern (update-or-insert) and description confirm this tool creates or modifies agent stages, which are configuration entities. This is a Write operation because changes are reversible—stages can be updated again or deleted.
From the tool's definition Tool name 'upsert_stage' and description 'Create or update a named stage in an agent' explicitly indicate reversible modification of agent configuration data.
Attacks that exploit this kind of access
Create or update a named stage in an agent. It is categorised as a Write tool in the BotUyo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BotUyo MCP Server MCP server in PolicyLayer and add a rule for upsert_stage: 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 BotUyo MCP Server. Nothing to install.
upsert_stage 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 upsert_stage 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 upsert_stage. 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.
upsert_stage is provided by the BotUyo MCP Server MCP server (marcoar1/botuyo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →