add_lead_area
Define a circular geographic area (name + centre lat/lng + radius km) for the leads map. leads_map then tags each mapped lead with the areas it falls in and rolls up lead counts + pipeline value per area.
This record as markdown: /tools/ai-featureboard-featureboard/add-lead-area.md
What add_lead_area does on FeatureBoard
AI agents use add_lead_area to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why add_lead_area is rated Medium
This tool creates or defines new geographic area records in the system, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could create incorrect geographic zones leading to flawed lead categorization and business intelligence, but the effect is limited to CRM metadata and is easily correctable.
From the tool's definition Tool description states it 'Define[s] a circular geographic area' with parameters (name, centre lat/lng, radius km), and the tool name is 'add_lead_area'. The verb 'add' and 'Define' indicate creation of new data.
Attacks that exploit this kind of access
The rule that runs add_lead_area safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_lead_area, this is the rule to start with:
add_lead_area stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every add_lead_area call is checked against it from then on.
Questions about add_lead_area
Define a circular geographic area (name + centre lat/lng + radius km) for the leads map. leads_map then tags each mapped lead with the areas it falls in and rolls up lead counts + pipeline value per area. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for add_lead_area: 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 FeatureBoard. Nothing to install.
add_lead_area is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_lead_area 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 add_lead_area. 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.
add_lead_area is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue