register_interest
Register demand for an unbuilt vertical. 500 signals triggers build queue activation. Include a contact channel so we can notify you when the vertical ships.
This record as markdown: /tools/dev-agent-module-mcp/register-interest.md
What register_interest does on Agent Module
AI agents use register_interest to create or update resources in Agent Module, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Module environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
contact | object | — | How to reach you when this vertical ships. String (email, webhook URL, agent card URL) or object { type, value, label }. Supported types: email, webhook, a2a, m |
agent_id | string | — | Your agent identifier (optional). |
use_case | string | — | Brief description of how you would use this vertical (optional). |
vertical | string | Yes | Vertical slug (e.g. "legal-contracts", "api-security"). |
Parameters from the server's own tool schema.
Why register_interest is rated Medium
This tool creates a new interest record in the system—a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete anything (Destructive), or move money (Financial). The blast radius is minimal: worst case, a user is added to a notification list, which is easily reversible and poses no security or operational risk.
From the tool's definition Tool description states it registers demand and includes a contact channel, indicating it creates or modifies a record in the system (an interest registration entry).
Attacks that exploit this kind of access
The rule that runs register_interest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Module, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For register_interest, this is the rule to start with:
register_interest stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Module, apply this rule, and every register_interest call is checked against it from then on.
Questions about register_interest
Register demand for an unbuilt vertical. 500 signals triggers build queue activation. Include a contact channel so we can notify you when the vertical ships. It is categorised as a Write tool in the Agent Module MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
register_interest accepts 4 parameters: contact, agent_id, use_case, vertical. Required: vertical. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Module MCP server in PolicyLayer and add a rule for register_interest: 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 Agent Module. Nothing to install.
register_interest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_interest 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 register_interest. 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.
register_interest is provided by the Agent Module MCP server (https://api.agent-module.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Module, and thousands of servers like it.
This server
Across the catalogue