Get information about your identity and available recipients.
AI agents call get_my_identity to retrieve information from MCP IDE Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata about the caller's identity and available communication recipients. It performs no creation, modification, deletion, code execution, or financial transactions. The information returned is already known or publicly available within the collaboration context, making unauthorized access a low blast radius concern. Misuse would only expose information the agent already has access to.
From the tool's definition Tool name 'get_my_identity' and description 'Get information about your identity and available recipients' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get information about your identity and available recipients. It is categorised as a Read tool in the MCP IDE Bridge MCP Server, which means it retrieves data without modifying state.
Register the MCP IDE Bridge MCP server in PolicyLayer and add a rule for get_my_identity: 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 IDE Bridge. Nothing to install.
get_my_identity 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 get_my_identity 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 get_my_identity. 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.
get_my_identity is provided by the MCP IDE Bridge MCP server (wiltshirek/mcp-ide-bridge). 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 →