detect_pattern_contamination
AI agents call detect_pattern_contamination to retrieve information from BigContext MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server's domain-agnostic analytical purpose and the pattern of sibling tools that perform validation/detection operations on documents without modifying them, this tool most likely performs pattern analysis or detection within documents to identify contamination or inconsistencies. This is a read-only analysis function with no side effects, making it a Read category risk.
From the tool's definition Tool name 'detect_pattern_contamination' and server context indicate document analysis and validation. The server's stated purpose is 'semantic analysis, epistemological validation, and extraction' of document fragments.
Attacks that exploit this kind of access
detect_pattern_contamination. It is categorised as a Read tool in the BigContext MCP MCP Server, which means it retrieves data without modifying state.
Register the BigContext MCP server in PolicyLayer and add a rule for detect_pattern_contamination: 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 BigContext MCP. Nothing to install.
detect_pattern_contamination 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 detect_pattern_contamination 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 detect_pattern_contamination. 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.
detect_pattern_contamination is provided by the BigContext MCP server (rixmerz/bigcontext_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 →