list_crm_inbox

List CRM inbox messages (newest-first), optionally filtered by status (pending/approved/rejected), company, and/or type (support/sales/contact/feedback/other).

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-crm-inbox.md

WHAT IT DOES

What list_crm_inbox does on FeatureBoard

AI agents call list_crm_inbox 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_crm_inbox is rated Low

This tool retrieves and queries CRM inbox messages with optional filtering parameters. It has no side effects—it does not create, modify, delete, or execute any operations. It is a straightforward data retrieval operation that fits the Read category.

From the tool's definition Tool name is 'list_crm_inbox' and description explicitly states it 'List[s] CRM inbox messages' with filtering options. The verb 'list' is a read-only retrieval operation with no modification, deletion, or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_crm_inbox Allowed

list_crm_inbox 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_crm_inbox": {}
  }
}

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_crm_inbox call is checked against it from then on.

FAQ

Questions about list_crm_inbox

What does the list_crm_inbox tool do? +

List CRM inbox messages (newest-first), optionally filtered by status (pending/approved/rejected), company, and/or type (support/sales/contact/feedback/other). 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_crm_inbox? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for list_crm_inbox: 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_crm_inbox? +

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

Can I rate-limit list_crm_inbox? +

Yes. Add a rate_limit block to the list_crm_inbox 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_crm_inbox completely? +

Set action: deny in the PolicyLayer policy for list_crm_inbox. 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_crm_inbox? +

list_crm_inbox 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 →