Listet verfügbare Semgrep-Regeln auf
AI agents call list_rules to retrieve information from Semgrep MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query/list operation to enumerate available Semgrep rules. This has no side effects—it simply retrieves existing data for inspection. No code is executed, no data is modified or deleted, and no external operations are triggered. This clearly falls under the Read category with low severity, as misuse would only expose informational content about available rules.
From the tool's definition Tool name is 'list_rules' and description states 'Listet verfügbare Semgrep-Regeln auf' (Lists available Semgrep rules). This is a read-only operation that retrieves and displays rule information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Listet verfügbare Semgrep-Regeln auf. It is categorised as a Read tool in the Semgrep MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semgrep MCP Server MCP server in PolicyLayer and add a rule for list_rules: 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 Semgrep MCP Server. Nothing to install.
list_rules 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_rules 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_rules. 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_rules is provided by the Semgrep MCP Server MCP server (stefanskiasan/semgrep-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 →