Check if a persona has specific permission for an action on a resource
AI agents call rbac-check-permission to retrieve information from MCP LLM Generator v2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a permission-checking utility that reads authorization state. It retrieves information about whether a persona is authorized, similar to a get or query operation. No data is created, modified, deleted, or executed as a result of calling this tool. The blast radius of misuse is minimal—an agent might incorrectly determine permissions, but the tool itself performs only a lookup.
From the tool's definition Tool name 'rbac-check-permission' and description 'Check if a persona has specific permission for an action on a resource' indicate a query/lookup operation.
Attacks that exploit this kind of access
Check if a persona has specific permission for an action on a resource. It is categorised as a Read tool in the MCP LLM Generator v2 MCP Server, which means it retrieves data without modifying state.
Register the MCP LLM Generator v2 MCP server in PolicyLayer and add a rule for rbac-check-permission: 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 LLM Generator v2. Nothing to install.
rbac-check-permission 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 rbac-check-permission 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 rbac-check-permission. 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.
rbac-check-permission is provided by the MCP LLM Generator v2 MCP server (mako10k/mcp-llm-generator). 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 →