Perform a protected action that requires authentication.
AI agents invoke protected_action to trigger actions in FastMCP OAuth Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool 'performs an action' which implies some side effect or execution, but the description is vague and uninformative about what the action actually does. 'Action' suggests more than a read operation, so Execute is the best fit given the available information.
From the tool's definition "Perform a protected action that requires authentication"
Attacks that exploit this kind of access
Perform a protected action that requires authentication. It is categorised as a Execute tool in the FastMCP OAuth Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FastMCP OAuth Server MCP server in PolicyLayer and add a rule for protected_action: 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 FastMCP OAuth Server. Nothing to install.
protected_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the protected_action 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 protected_action. 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.
protected_action is provided by the FastMCP OAuth Server MCP server (jcamier/mcp-oauth). 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 →