get_my_permissions
AI agents call get_my_permissions to retrieve information from Clink 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 permission information about the user—a read-only operation with no side effects. Even if an AI agent misuses it, the worst outcome is viewing information it shouldn't access, which is a low-severity information disclosure risk. Confidence is reduced from 0.85 to 0.7 due to the empty description, which limits verification of actual functionality.
From the tool's definition Tool name is 'get_my_permissions' which indicates a retrieval/query operation. The description is empty, but the naming convention and the context of a collaboration/messaging platform suggest this queries permission data for the current user without…
Attacks that exploit this kind of access
get_my_permissions. It is categorised as a Read tool in the Clink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for get_my_permissions: 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 Clink MCP Server. Nothing to install.
get_my_permissions 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_permissions 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_permissions. 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_permissions is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). 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 →