log_rbac_violation · MCPDischarge MCP: Risk & Policy

WHAT IT DOES

What log_rbac_violation does on MCPDischarge

AI agents use log_rbac_violation to create or update resources in MCPDischarge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPDischarge environment.

WHY IT NEEDS A POLICY

Why log_rbac_violation needs a policy

This tool writes a new RBAC violation record to an audit log. It is a Write operation since it creates data in a logging/auditing system. The severity is medium because misuse could allow an attacker to inject false security violation records, pollute audit trails, or mask real violations by flooding the log — undermining the integrity of the hospital's access control monitoring.

From the tool's definition 'Manually log an RBAC violation for auditing or testing' — creates a log entry (write operation) in an audit/security system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_rbac_violation Rate-limited

log_rbac_violation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_rbac_violation": {
      "limits": [
        {
          "counter": "log_rbac_violation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCPDischarge, so you can run agents against it safely.

FAQ

Questions about log_rbac_violation

What does the log_rbac_violation tool do? +

Manually log an RBAC violation for auditing or testing. It is categorised as a Write tool in the MCPDischarge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_rbac_violation? +

Register the MCPDischarge MCP server in PolicyLayer and add a rule for log_rbac_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 MCPDischarge. Nothing to install.

What risk level is log_rbac_violation? +

log_rbac_violation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_rbac_violation? +

Yes. Add a rate_limit block to the log_rbac_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.

How do I block log_rbac_violation completely? +

Set action: deny in the PolicyLayer policy for log_rbac_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.

What MCP server provides log_rbac_violation? +

log_rbac_violation is provided by the MCPDischarge MCP server (prashantsingh1234/mcp_project). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.