list_leads
AI agents call list_leads to retrieve information from Multilead Open API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name 'list_leads', this is a read operation that retrieves or queries lead data from the Multilead platform. No side effects are indicated or implied by the function name. The low severity reflects that retrieving lead information poses minimal risk even if accessed by an AI agent, as it only exposes existing data rather than modifying, deleting, or executing operations.
From the tool's definition Tool name 'list_leads' indicates a retrieval operation that queries lead data without modification. The verb 'list' is a standard read operation. Description is empty but the name strongly suggests data retrieval with no side effects.
Attacks that exploit this kind of access
list_leads. It is categorised as a Read tool in the Multilead Open API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for list_leads: 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 Multilead Open API MCP Server. Nothing to install.
list_leads 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 list_leads 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 list_leads. 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.
list_leads is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-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 →