Search the marketplace for scripts matching a natural language query.
AI agents call search_scripts to retrieve information from Vending Machine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing script data from a marketplace based on search criteria. It performs no write operations, does not execute code, and does not modify state. It is a straightforward read operation that returns search results, fitting the Read category with low severity since misuse would only result in unwanted information retrieval.
From the tool's definition Tool description explicitly states 'Search the marketplace for scripts matching a natural language query.' The verb 'search' indicates retrieval/querying of data with no modification or side effects.
Attacks that exploit this kind of access
Search the marketplace for scripts matching a natural language query. It is categorised as a Read tool in the Vending Machine MCP Server, which means it retrieves data without modifying state.
Register the Vending Machine MCP server in PolicyLayer and add a rule for search_scripts: 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.
search_scripts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_scripts 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 search_scripts. 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.
search_scripts 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 →