Call this when: (a) a user reports that harmful content received a safe verdict, (b) a downstream system detects an issue that scanning missed (e.g., a WAF blocks a request that Shrike allowed), or (c) post-processing analysis reveals content that should have been caught. Supports multiple bypas...
Accepts file system path (filePath); Bulk/mass operation — affects multiple targets
Part of the Shrike Security MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use report_bypass to create or modify resources in Shrike Security. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call report_bypass repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Shrike Security.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
report_bypass:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Shrike Security policy for all 12 tools.
Agents calling write-class tools like report_bypass have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Call this when: (a) a user reports that harmful content received a safe verdict, (b) a downstream system detects an issue that scanning missed (e.g., a WAF blocks a request that Shrike allowed), or (c) post-processing analysis reveals content that should have been caught. Supports multiple bypass types: - Prompt bypasses: Use 'prompt' field - File write bypasses: Use 'filePath' and/or 'fileContent' fields - SQL bypasses: Use 'sqlQuery' field - Web search bypasses: Use 'searchQuery' field Include mutationType if known (semantic_rewrite, encoding_exploit, unicode_tricks, etc.) and category for better classification. The bypass is analyzed and may generate a new detection pattern via ThreatSense adaptive learning. Enterprise context: Every bypass report strengthens detection for all users. Security teams can track bypass patterns over time for compliance reporting and coverage gap analysis. ERROR HANDLING: If this tool returns an error, log the bypass details locally and retry later. Bypass reports are non-blocking — do NOT halt your pipeline on report_bypass failure.. It is categorised as a Write tool in the Shrike Security MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for report_bypass. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Shrike Security MCP server.
report_bypass is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the report_bypass rule in your Intercept 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 Intercept policy for report_bypass. 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.
report_bypass is provided by the Shrike Security MCP server (shrike-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept