add
AI agents call add as a supporting operation in Auth0 OAuth MCP Server workflows.
The description is empty and the name 'add' alone is ambiguous — it could mean adding numbers (like calculate), adding records (Write), or something else entirely. With no description, confidence is very low. Given the sibling tool 'calculate' exists, 'add' may be a simple arithmetic operation (Other/Read), but this cannot be confirmed. Defaulting to Other with minimal severity due to lack of evidence.
From the tool's definition Tool name is 'add' with an empty description. No information is available about what this tool does.
Attacks that exploit this kind of access
add. It is categorised as a Other tool in the Auth0 OAuth MCP Server MCP Server, which means it performs auxiliary operations.
Register the Auth0 OAuth MCP Server 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 Auth0 OAuth MCP Server. Nothing to install.
add is a Other tool with low risk. Read-only tools are generally safe to allow by default.
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 Auth0 OAuth MCP Server MCP server (pratham-svg/mcp-oauth). 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 →