Browse a specific user
AI agents call browse-user-history 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 historical user data from an archive without any side effects or capability to modify, delete, or execute external operations. It is a read-only operation similar to sibling tools like 'lookup-profile' and 'search-archive'. The blast radius is minimal as it only exposes already-public archived information.
From the tool's definition Tool enables 'browsing' and 'retrieving' user data from archived Twitter content; the description explicitly states the server is for 'searching and retrieving preserved' data with no modification or deletion capabilities mentioned.
Attacks that exploit this kind of access
Browse a specific 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 browse-user-history: 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.
browse-user-history 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 browse-user-history 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 browse-user-history. 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.
browse-user-history 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 →