Check which sales intelligence services are configured and available. Returns the configuration status of each integrated service (Gong, ZoomInfo, Clay, LinkedIn). Use this to verify which tools are ready to use before running queries. Args: None Returns: Status of each service (configured/not co...
AI agents call sales_intel_status to retrieve information from Sales Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a purely informational read operation that queries the configuration state of integrated services. It retrieves data without modifying, executing operations, or causing side effects. The low severity reflects minimal blast radius—an agent misusing this tool can only see which services are enabled, which is not sensitive.
From the tool's definition Tool description states it 'Check[s] which sales intelligence services are configured and available' and 'Returns the configuration status of each integrated service'. The tool takes no arguments and returns status information only, with no side effects.
Attacks that exploit this kind of access
Check which sales intelligence services are configured and available. Returns the configuration status of each integrated service (Gong, ZoomInfo, Clay, LinkedIn). Use this to verify which tools are ready to use before running queries. Args: None Returns: Status of each service (configured/not configured) with required environment variables. It is categorised as a Read tool in the Sales Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Sales Intelligence MCP server in PolicyLayer and add a rule for sales_intel_status: 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 Sales Intelligence. Nothing to install.
sales_intel_status 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 sales_intel_status 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 sales_intel_status. 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.
sales_intel_status is provided by the Sales Intelligence MCP server (jbalbu01/sales-intelligence-mcp-server). 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 →