Get the current API key context on PostEverywhere — who you are, what scopes your key has, what plan the organization is on, and what
AI agents call get_me to retrieve information from Posteverywhere 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 current API key and organization context. It has no side effects, does not modify data, and does not trigger external operations. It is purely informational retrieval, fitting the 'Read' category. The low severity reflects that disclosure of this metadata alone has limited blast radius, though it could inform further attacks. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'get_me' and description indicates it retrieves current API context information (identity, scopes, plan details) without modifying anything. Uses words 'Get' and retrieves read-only metadata about the authenticated session.
Attacks that exploit this kind of access
Get the current API key context on PostEverywhere — who you are, what scopes your key has, what plan the organization is on, and what. It is categorised as a Read tool in the Posteverywhere MCP Server, which means it retrieves data without modifying state.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for get_me: 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 Posteverywhere. Nothing to install.
get_me 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_me 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_me. 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_me is provided by the Posteverywhere MCP server (posteverywhere/mcp). 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 →