Get when and how to apply @RequiresPermission, owner bypass rules, cache invalidation patterns, and multi-tenant scoping behaviour.
AI agents call rbac_get_guard_usage to retrieve information from LaunchFrame MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project-specific implementation details and architectural guidance related to permission guards and RBAC patterns. It performs read-only queries against a knowledge base to inform code generation and implementation decisions. No data is created, modified, deleted, executed, or changed as a result of calling this tool.
From the tool's definition Tool description indicates retrieval of architectural knowledge: 'Get when and how to apply @RequiresPermission, owner bypass rules, cache invalidation patterns, and multi-tenant scoping behaviour.' The verb 'Get' and the nature of information retrieved…
Attacks that exploit this kind of access
Get when and how to apply @RequiresPermission, owner bypass rules, cache invalidation patterns, and multi-tenant scoping behaviour. It is categorised as a Read tool in the LaunchFrame MCP MCP Server, which means it retrieves data without modifying state.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for rbac_get_guard_usage: 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 LaunchFrame MCP. Nothing to install.
rbac_get_guard_usage 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_get_guard_usage 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_get_guard_usage. 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_get_guard_usage is provided by the LaunchFrame MCP server (launchframe-dev/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 →