get_leads_from_campaign
AI agents call get_leads_from_campaign 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.
This tool retrieves or queries lead data from a campaign, consistent with Read category operations. There are no indications of data modification, deletion, execution, or financial impact. The empty description slightly reduces confidence, but the naming convention and platform context support classification as a straightforward read operation with low severity.
From the tool's definition Tool name 'get_leads_from_campaign' indicates a retrieval operation; the verb 'get' is a standard read-only operation.
Attacks that exploit this kind of access
get_leads_from_campaign. 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 get_leads_from_campaign: 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.
get_leads_from_campaign 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 get_leads_from_campaign 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 get_leads_from_campaign. 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.
get_leads_from_campaign 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 →