AI agents call getUserProfile to retrieve information from MCP Authentication Demo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information for an already-authenticated user. It is a simple read operation that queries and returns existing data without creating, modifying, deleting, or executing anything. The low severity reflects that user profile data, while potentially sensitive, is typically limited in scope and does not enable destructive or financial actions.
From the tool's definition Tool name 'getUserProfile' and description 'Returns the authenticated user' indicate a data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access getUserProfile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Authentication Demo, and nothing reaches the server without passing your rules. This is the rule we recommend for getUserProfile:
{
"version": "1",
"default": "deny",
"tools": {
"getUserProfile": {}
}
}getUserProfile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the authenticated user. It is categorised as a Read tool in the MCP Authentication Demo MCP Server, which means it retrieves data without modifying state.
Register the MCP Authentication Demo MCP server in PolicyLayer and add a rule for getUserProfile: 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 Authentication Demo. Nothing to install.
getUserProfile 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 getUserProfile 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 getUserProfile. 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.
getUserProfile is provided by the MCP Authentication Demo MCP server (workos/vercel-mcp-example). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Authentication Demo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 MCP Authentication Demo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.