add
AI agents call add as a supporting operation in MCP Server workflows.
With no description and only a generic name 'add', it is impossible to reliably determine what this tool does. Sibling tools (askMastra, getDiceRoll) suggest a mixed-purpose server. 'add' could mean adding numbers, adding configuration, adding records, or something else entirely. Defaulting to Other with very low confidence due to complete lack of information.
From the tool's definition Tool name is 'add' with no description provided. The server description mentions MCP functionality, Node.js, and Docker environments but gives no specific insight into what 'add' does.
Attacks that exploit this kind of access
add. It is categorised as a Other tool in the MCP Server MCP Server, which means it performs auxiliary operations.
Register the 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 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 MCP Server MCP server (jeongjaesoon/sample-mcp-server). 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 →