get_nurture_status
Get the automated nurture email sequence status for leads. Shows pending, sent, failed, and skipped emails. Businys automatically sends follow-up email sequences to captured leads.
This record as markdown: /tools/app-businys-mcp-server/get-nurture-status.md
What get_nurture_status does on Businys
AI agents call get_nurture_status to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_nurture_status is rated Low
This tool queries the state of automated nurture email sequences for leads. It has no side effects—it only retrieves and displays status information. There is no creation, modification, deletion, execution, or financial impact. This is a straightforward read operation against a CRM/lead management system, appropriate for a business management platform managing client relationships.
From the tool's definition get_nurture_status retrieves email sequence status information showing pending, sent, failed, and skipped emails. The description uses 'Get' and 'Shows', indicating data retrieval with no modification or execution of operations.
Attacks that exploit this kind of access
The rule that runs get_nurture_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_nurture_status, this is the rule to start with:
get_nurture_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every get_nurture_status call is checked against it from then on.
Questions about get_nurture_status
Get the automated nurture email sequence status for leads. Shows pending, sent, failed, and skipped emails. Businys automatically sends follow-up email sequences to captured leads. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for get_nurture_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 Businys. Nothing to install.
get_nurture_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 get_nurture_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 get_nurture_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.
get_nurture_status is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue