Use this when ChatGPT needs the authenticated user
AI agents call identity.profile to retrieve information from GPT MCP Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple data retrieval tool that returns profile information about the authenticated user. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an AI agent could only access the authenticated user's already-authorized profile data, which is a read-only operation. Classified as Read with low severity.
From the tool's definition Tool retrieves the authenticated user's profile data. The name 'identity.profile' and description 'Use this when ChatGPT needs the authenticated user' indicate a query/retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Use this when ChatGPT needs the authenticated user. It is categorised as a Read tool in the GPT MCP Service MCP Server, which means it retrieves data without modifying state.
Register the GPT MCP Service MCP server in PolicyLayer and add a rule for identity.profile: 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 GPT MCP Service. Nothing to install.
identity.profile 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 identity.profile 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 identity.profile. 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.
identity.profile is provided by the GPT MCP Service MCP server (jmillpps/encore-mcp-base). 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 →