list_leads

List leads (newest-first), optionally filtered by pipeline status and/or company.

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/list-leads.md

WHAT IT DOES

What list_leads does on FeatureBoard

AI agents call list_leads to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_leads is rated Low

This tool retrieves and queries lead data with optional filtering parameters. It has no capability to create, modify, delete, or execute operations. The read-only nature and lack of side effects place it firmly in the Read category with low severity risk.

From the tool's definition Tool name is 'list_leads' and description states 'List leads...optionally filtered by pipeline status and/or company.' The verb 'list' and the action of retrieving/filtering existing data indicates query-only functionality with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_leads 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 list_leads, this is the rule to start with:

list_leads Allowed

list_leads is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_leads": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every list_leads call is checked against it from then on.

FAQ

Questions about list_leads

What does the list_leads tool do? +

List leads (newest-first), optionally filtered by pipeline status and/or company. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_leads? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for list_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 FeatureBoard. Nothing to install.

What risk level is list_leads? +

list_leads is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_leads? +

Yes. Add a rate_limit block to the list_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.

How do I block list_leads completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_leads? +

list_leads 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.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →