Check for new leads added in last 24 hours that need welcome emails
AI agents call check_new_leads to retrieve information from Revenue Engine MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a lead database to retrieve newly added leads within a time window. It performs a search/list operation with no side effects—no data is created, modified, deleted, or executed. The purpose is informational (identifying leads for potential follow-up), making it a classic Read category tool.
From the tool's definition Tool description states 'Check for new leads' which is a query/retrieval operation. The phrase 'that need welcome emails' describes a filtering criterion, not an action the tool performs. The tool retrieves and lists data without modifying it.
Attacks that exploit this kind of access
Check for new leads added in last 24 hours that need welcome emails. It is categorised as a Read tool in the Revenue Engine MCP MCP Server, which means it retrieves data without modifying state.
Register the Revenue Engine MCP server in PolicyLayer and add a rule for check_new_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 Revenue Engine MCP. Nothing to install.
check_new_leads 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 check_new_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.
Set action: deny in the PolicyLayer policy for check_new_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.
check_new_leads is provided by the Revenue Engine MCP server (promptishoperations/mcpspec). 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 →