Get leads from the CRM pipeline. Can filter by stage and vendedor.
AI agents call get_leads to retrieve information from Outlet das Cores CRM without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries CRM lead data with optional filtering. It performs no modifications, deletions, or external operations. It is a standard Read operation with minimal blast radius—an AI agent using it could only access existing lead information, which may be sensitive but cannot be altered or deleted through this tool alone.
From the tool's definition Tool name 'get_leads' and description 'Get leads from the CRM pipeline. Can filter by stage and vendedor.' indicate a retrieval/query operation with no side effects. Filtering parameters (stage, vendedor) do not alter data.
Attacks that exploit this kind of access
Get leads from the CRM pipeline. Can filter by stage and vendedor. It is categorised as a Read tool in the Outlet das Cores CRM MCP Server, which means it retrieves data without modifying state.
Register the Outlet das Cores CRM MCP server in PolicyLayer and add a rule for get_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 Outlet das Cores CRM. Nothing to install.
get_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 get_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 get_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.
get_leads is provided by the Outlet das Cores CRM MCP server (oeduardomanoel/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 →