Find specific roles/positions within a company. Targeted search for particular job titles or functions within organizations.
AI agents call find_role to retrieve information from LeadMagic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for and retrieves information about job roles/positions within companies. It queries existing data without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—returning employment information that may already be public or proprietary but not causing irreversible damage or financial harm. This is a standard Read-category data enrichment query.
From the tool's definition Tool description states 'Targeted search for particular job titles or functions within organizations' - a query/search operation with no data modification capability. The verb 'find' and context of 'search' indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access find_role gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LeadMagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_role:
{
"version": "1",
"default": "deny",
"tools": {
"find_role": {}
}
}find_role is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find specific roles/positions within a company. Targeted search for particular job titles or functions within organizations. It is categorised as a Read tool in the LeadMagic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LeadMagic MCP Server MCP server in PolicyLayer and add a rule for find_role: 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 LeadMagic MCP Server. Nothing to install.
find_role 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 find_role 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 find_role. 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.
find_role is provided by the LeadMagic MCP Server MCP server (leadmagic/leadmagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LeadMagic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 LeadMagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.