Get plan tasks for a specific lead.
AI agents call getPlanTasksByLead to retrieve information from Lofty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns plan tasks associated with a lead. It performs no data modification, deletion, or external execution—only fetches and returns existing information. The 'Get' operation is a standard read pattern with minimal risk when exposed to an AI agent, assuming the agent has appropriate authorization for the lead being queried.
From the tool's definition Tool name 'getPlanTasksByLead' and description 'Get plan tasks for a specific lead' indicate a retrieval operation with the verb 'Get', which retrieves data without modifying it.
Attacks that exploit this kind of access
Get plan tasks for a specific lead. It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for getPlanTasksByLead: 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 Lofty MCP Server. Nothing to install.
getPlanTasksByLead 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 getPlanTasksByLead 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 getPlanTasksByLead. 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.
getPlanTasksByLead is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-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 →