Get the exact decorator and import for a specific auth need.
AI agents call auth_get_decorator_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.
The tool retrieves existing auth decorator patterns and imports for reference purposes. It does not execute code, trigger external operations, modify data, delete anything, or move money. This is a straightforward Read category with low severity since misuse (e.g., requesting a decorator for the wrong auth scheme) has no irreversible side effects — it simply returns information.
From the tool's definition Tool name contains 'get' and description states 'Get the exact decorator and import' — this is a retrieval operation that queries architectural/configuration data without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Get the exact decorator and import for a specific auth need. 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 auth_get_decorator_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.
auth_get_decorator_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 auth_get_decorator_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 auth_get_decorator_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.
auth_get_decorator_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 →