Filtert Scan-Ergebnisse nach verschiedenen Kriterien
AI agents call filter_results 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.
This tool queries and filters existing scan results from Semgrep without modifying, deleting, or executing any operations. It is a pure read operation that retrieves a subset of data based on specified criteria, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'filter_results' and description 'Filters scan results according to various criteria' indicate a data retrieval and filtering operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Filtert Scan-Ergebnisse nach verschiedenen Kriterien. 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 filter_results: 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.
filter_results 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 filter_results 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 filter_results. 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.
filter_results 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 →