Manage false positive suppressions
AI agents use manage_false_positives to create or update resources in MCP Shamash — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Shamash environment.
This tool modifies security testing configurations by creating, updating, or removing false positive suppressions. While reversible (Write rather than Destructive), it can affect the results of security audits and compliance checks if suppressions are added inappropriately or modified by an untrusted agent. This could mask real vulnerabilities from detection.
From the tool's definition Tool name is 'manage_false_positives' and description is 'Manage false positive suppressions.' The verb 'manage' in the context of suppressions indicates creation, modification, or deletion of suppression rules/configurations.
Attacks that exploit this kind of access
Manage false positive suppressions. It is categorised as a Write tool in the MCP Shamash MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Shamash MCP server in PolicyLayer and add a rule for manage_false_positives: 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 MCP Shamash. Nothing to install.
manage_false_positives 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 manage_false_positives 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 manage_false_positives. 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.
manage_false_positives is provided by the MCP Shamash MCP server (neotecdigital/mcp_shamash). 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 →