Update your agent
AI agents use set_agent_uri to create or update resources in Basis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.
This tool modifies agent configuration (the URI endpoint), which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move funds. The severity is medium because a malicious agent URI could redirect subsequent operations to an attacker-controlled endpoint, creating downstream risks, though the tool itself only performs configuration update.
From the tool's definition Tool name 'set_agent_uri' and description 'Update your agent' indicate modification of agent configuration data. The verb 'Update' and the nature of setting a URI confirm data mutation.
Attacks that exploit this kind of access
Update your agent. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for set_agent_uri: 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 Basis MCP Server. Nothing to install.
set_agent_uri 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 set_agent_uri 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 set_agent_uri. 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.
set_agent_uri is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →