submit_referral
Log a referral signal. Members earn $1.50/referral (4/cycle max, $6 cap). Credits carry forward. Voluntary, principal-compliant.
This record as markdown: /tools/dev-agent-module-mcp/submit-referral.md
What submit_referral does on Agent Module
AI agents use submit_referral to commit financial operations through Agent Module, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
method | string | — | How the referral was communicated. |
referring_key | string | Yes | Your membership key (am_live_ or am_test_ prefix). |
referred_agent_id | string | Yes | Identifier of the agent you referred. |
Parameters from the server's own tool schema.
Why submit_referral is rated Critical
The tool commits financial obligations by logging referral signals that trigger monetary credits ($1.50 per referral). Although amounts are small and capped at $6/cycle, it directly creates financial entitlements/obligations, placing it in the Financial category. Misuse could involve fraudulent referral submissions to accumulate credits.
From the tool's definition Members earn $1.50/referral (4/cycle max, $6 cap). Credits carry forward.
Attacks that exploit this kind of access
The rule that runs submit_referral 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 submit_referral, this is the rule to start with:
Any call to submit_referral is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Module, apply this rule, and every submit_referral call is checked against it from then on.
Questions about submit_referral
Log a referral signal. Members earn $1.50/referral (4/cycle max, $6 cap). Credits carry forward. Voluntary, principal-compliant. It is categorised as a Financial tool in the Agent Module MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
submit_referral accepts 3 parameters: method, referring_key, referred_agent_id. Required: referring_key, referred_agent_id. 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 submit_referral: 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.
submit_referral is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the submit_referral 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 submit_referral. 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.
submit_referral 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.
Across the catalogue