Check if a planned action violates production-only policy. Includes inline suggestions, context-aware scoring, and explanations.
AI agents call ember_check_violation to retrieve information from Agent Runtime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes whether an action violates policy constraints. It produces no side effects, creates no resources, executes no external operations, and modifies no state. The 'check' and 'scoring' language confirms it is a Read category tool for policy validation. Severity is low because misuse would yield informational output (policy guidance) rather than operational harm.
From the tool's definition Tool name and description indicate 'check' and 'violation' assessment with 'suggestions, context-aware scoring, and explanations' — a purely evaluative/query operation. No execution, modification, or deletion occurs; the tool queries policy compliance status.
Attacks that exploit this kind of access
Check if a planned action violates production-only policy. Includes inline suggestions, context-aware scoring, and explanations. It is categorised as a Read tool in the Agent Runtime MCP Server, which means it retrieves data without modifying state.
Register the Agent Runtime MCP server in PolicyLayer and add a rule for ember_check_violation: 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 Agent Runtime. Nothing to install.
ember_check_violation 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 ember_check_violation 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 ember_check_violation. 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.
ember_check_violation is provided by the Agent Runtime MCP server (marc-shade/agent-runtime-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 →