AI agents use set-api-url to create or update resources in PI API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PI API MCP Server environment.
This tool modifies API endpoint configuration, which is a reversible write operation affecting how all subsequent requests are routed. While not directly creating or deleting data, it changes system configuration that could redirect requests to unintended servers if misconfigured by an agent.
From the tool's definition Tool name 'set-api-url' and description 'Set the API base URL for all requests' indicate modification of configuration state that persists across subsequent API calls.
Documented attack patterns abuse exactly the kind of access set-api-url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PI API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set-api-url:
{
"version": "1",
"default": "deny",
"tools": {
"set-api-url": {
"limits": [
{
"counter": "set-api-url_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set-api-url 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 the API base URL for all requests. It is categorised as a Write tool in the PI API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PI API MCP Server MCP server in PolicyLayer and add a rule for set-api-url: 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 PI API MCP Server. Nothing to install.
set-api-url 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-api-url 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-api-url. 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-api-url is provided by the PI API MCP Server MCP server (mingzilla/pi-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PI API MCP Server, 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.
18 PI API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.