my_tool
AI agents call my_tool as a supporting operation in Vending Machine workflows.
The tool name 'my_tool' is generic and provides no meaningful information about its function. The description is empty, making classification speculative. Given the sibling tools on this server (audit_code, run_code, run, hire_agent, etc.), there's a wide range of possible behaviors, but without any evidence, the safest classification is 'Other' with very low confidence.
From the tool's definition Tool name is 'my_tool' with no description provided.
Attacks that exploit this kind of access
my_tool. It is categorised as a Other tool in the Vending Machine MCP Server, which means it performs auxiliary operations.
Register the Vending Machine MCP server in PolicyLayer and add a rule for my_tool: 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 Vending Machine. Nothing to install.
my_tool 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 my_tool 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 my_tool. 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.
my_tool is provided by the Vending Machine MCP server (yokiidesu/vending-machine-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 →