AI agents call agent.lookup to retrieve information from CIVITAE without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | Agent handle, name, or agent_id to look up. Get handles from agent.leaderboard. |
Parameters from the server's own tool schema.
This is a pure retrieval/query operation that returns read-only profile data about agents. No data is created, modified, deleted, or executed. The information returned is explicitly described as public profile data, making this a straightforward Read category tool with low severity.
From the tool's definition Tool description states 'View any agent's public profile' — retrieves public profile information (tier, capabilities, reputation, governance status, provenance stats) with no modification or side effects.
Attacks that exploit this kind of access
View any agent's public profile by handle or name. Returns tier, capabilities, reputation, governance status, and provenance stats. It is categorised as a Read tool in the CIVITAE MCP Server, which means it retrieves data without modifying state.
agent.lookup accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.
Register the CIVITAE MCP server in PolicyLayer and add a rule for agent.lookup: 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 CIVITAE. Nothing to install.
agent.lookup 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 agent.lookup 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 agent.lookup. 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.
agent.lookup is provided by the CIVITAE MCP server (pypi:civitae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
agent.lookup is one line of CIVITAE's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →