AI agents use add_provider to create or update resources in Unlimited — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unlimited environment.
'add_' prefix indicates a creation/modification operation (Write category). The broader system context—involving agent delegation, queue management, and policy controls—suggests that adding a provider could affect job routing, authentication, or resource access. Without explicit evidence of destructive deletion, financial transactions, or code execution, Write is the most appropriate classification.
From the tool's definition Tool name 'add_provider' suggests adding or registering a provider entity. In the context of a server that 'delegates coding and sysops work to cheaper agents via durable background queues,' this likely creates or modifies provider configurations.
Attacks that exploit this kind of access
add_provider. It is categorised as a Write tool in the Unlimited MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unlimited MCP server in PolicyLayer and add a rule for add_provider: 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 Unlimited. Nothing to install.
add_provider 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_provider 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_provider. 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_provider is provided by the Unlimited MCP server (triumsebas/unlimited-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 →