add
AI agents call add as a supporting operation in Market Price Finder workflows.
The description is empty and the name 'add' is ambiguous. On a Market Price Finder server, sibling tools suggest read/query operations. 'add' could mean adding a product to track, adding to a list, or something else. Without any description, confidence is very low.
From the tool's definition Tool name is 'add' with an empty description on a Market Price Finder server. No description to indicate what it does.
Attacks that exploit this kind of access
add. It is categorised as a Other tool in the Market Price Finder MCP Server, which means it performs auxiliary operations.
Register the Market Price Finder 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 Market Price Finder. 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 Market Price Finder MCP server (robuno/market-finder-ts-mcp-remote-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 →