rc_sequence_enroll
Enroll an email into a sequence. Records the enrollment locally; if the sequence is bound to a CRM workflow + location, also POSTs the contact to the CRM. Idempotent — won
This record as markdown: /tools/io-github-0nork-0nmcp/rc-sequence-enroll.md
What rc_sequence_enroll does on 0nmcp
AI agents call rc_sequence_enroll to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why rc_sequence_enroll is rated Low
Even though rc_sequence_enroll only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs rc_sequence_enroll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rc_sequence_enroll, this is the rule to start with:
rc_sequence_enroll 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 0nmcp, apply this rule, and every rc_sequence_enroll call is checked against it from then on.
Questions about rc_sequence_enroll
Enroll an email into a sequence. Records the enrollment locally; if the sequence is bound to a CRM workflow + location, also POSTs the contact to the CRM. Idempotent — won. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for rc_sequence_enroll: 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 0nmcp. Nothing to install.
rc_sequence_enroll 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 rc_sequence_enroll 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 rc_sequence_enroll. 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.
rc_sequence_enroll is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue