AI agents call list_scripts to retrieve information from MCPMake without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about registered scripts without creating, modifying, deleting, or executing anything. It is a straightforward enumeration/listing operation typical of Read category tools. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes metadata about available scripts rather than executing them or modifying data.
From the tool's definition Tool name 'list_scripts' and description 'List all registered scripts with brief descriptions' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all registered scripts with brief descriptions. It is categorised as a Read tool in the MCPMake MCP Server, which means it retrieves data without modifying state.
Register the MCPMake MCP server in PolicyLayer and add a rule for list_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 MCPMake. Nothing to install.
list_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 list_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 list_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.
list_scripts is provided by the MCPMake MCP server (shex1627/mcpmake). 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 →