Retrieve all messages for a specific lead
AI agents call get_lead_messages 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 performs a straightforward query operation to fetch historical message data associated with a lead. It has no capability to modify, delete, or trigger external actions—only to read and return existing data. The blast radius of misuse is minimal; an AI agent could only access lead message history, which poses no operational, financial, or destructive risk.
From the tool's definition Tool name 'get_lead_messages' and description 'Retrieve all messages for a specific lead' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve all messages for a specific lead. 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_lead_messages: 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_lead_messages 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_lead_messages 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_lead_messages. 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_lead_messages 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 →