Get the authenticated user
AI agents call user.current to retrieve information from Freedcamp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data about the authenticated user (a read-only query). There are no side effects, data modifications, code execution, destructive actions, or financial implications. The blast radius is minimal—an AI agent obtaining the current user's identity poses negligible security risk. This is a standard authentication/identity lookup operation.
From the tool's definition Tool name 'user.current' and description 'Get the authenticated user' indicate a retrieval operation that queries user identity information without modification or execution of external operations.
Attacks that exploit this kind of access
Get the authenticated user. It is categorised as a Read tool in the Freedcamp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Freedcamp MCP Server MCP server in PolicyLayer and add a rule for user.current: 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 Freedcamp MCP Server. Nothing to install.
user.current 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 user.current 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 user.current. 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.
user.current is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). 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 →