get_violations
AI agents call get_violations to retrieve information from PolicyPulse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries compliance violation data from Kubernetes policy engines without modifying state or executing external operations. This is a Read operation.
From the tool's definition Tool name 'get_violations' and server context indicate retrieval of policy violation data from Kubernetes policy engines.
Attacks that exploit this kind of access
get_violations. It is categorised as a Read tool in the PolicyPulse MCP MCP Server, which means it retrieves data without modifying state.
Register the PolicyPulse MCP server in PolicyLayer and add a rule for get_violations: 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 PolicyPulse MCP. Nothing to install.
get_violations 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 get_violations 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 get_violations. 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.
get_violations is provided by the PolicyPulse MCP server (raviteja-pegata/policy-pulse-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 →