Look up a Twitter user
AI agents call lookup-profile to retrieve information from Community Archive 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 user profile information from archived Twitter data with no side effects. It performs a lookup query against preserved data, which is a classic Read operation. The low severity reflects that exposing archived user profile data carries minimal risk of harm—it is already public historical information in a read-only archive context.
From the tool's definition Tool is described as 'Look up a Twitter user' on a server that 'Enables searching and retrieving preserved Twitter data' without any modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Look up a Twitter user. It is categorised as a Read tool in the Community Archive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Community Archive MCP Server MCP server in PolicyLayer and add a rule for lookup-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 Community Archive MCP Server. Nothing to install.
lookup-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 lookup-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 lookup-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.
lookup-profile is provided by the Community Archive MCP Server MCP server (vivalapanda/archive-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 →