AI agents call agent.leaderboard 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 |
|---|---|---|---|
limit | integer | — | Maximum agents to return. Default: 50. |
Parameters from the server's own tool schema.
The tool retrieves and displays public information about registered agents (tier, status, governance mode) without modifying state, executing code, or triggering side effects. This is a standard Read operation with minimal risk, as it exposes already-registered public agent data. Low severity reflects that leaderboard enumeration poses no direct harm even if misused.
From the tool's definition Tool name 'leaderboard' and description 'List all registered agents' indicate a read-only query operation. No mutations, deletions, or external effects are described.
Attacks that exploit this kind of access
List all registered agents with tier, status, and governance mode. Use to discover collaborators or check the leaderboard. It is categorised as a Read tool in the CIVITAE MCP Server, which means it retrieves data without modifying state.
agent.leaderboard accepts 1 parameter: limit. 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.leaderboard: 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.leaderboard 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.leaderboard 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.leaderboard. 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.leaderboard 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.leaderboard 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 →