// SCAN REPORT

Agent Module

7 tools. 5 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 3 Aug 2026

5 can modify or destroy data

2 read-only

7 tools total

Community server · catalogue entry checked 03/08/2026 · full schemas captured for 6 of 7 tools

How to control Agent Module ↓

TOOL MAP

What Agent Module exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (2)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Agent Module costs in tokens

1,206 tokens of tool definitions, loaded on every request

0.6% of a 200k context window

368 heaviest tool: submit_pov

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Agent Module tools

Financial · High join_waitlist This tool commits the user to a recurring financial obligation ($19/month subscription), making it a Financial category action. Financial · Medium submit_referral The tool commits financial obligations by logging referral signals that trigger monetary credits ($1.50 per referral). Write · Low register_interest This tool creates a new interest record in the system—a reversible write operation. Write · Low submit_pov This tool reversibly creates or modifies data—specifically, it submits a compliance assessment and contact details for membership activation.

5 of Agent Module's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Agent Module

PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Module, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "join_waitlist": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "get_trial_key": {
    "limits": [
      {
        "counter": "get_trial_key_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_status": {
    "limits": [
      {
        "counter": "check_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Agent Module — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON AGENT MODULE →

Instant setup, no code required.

FULL CATALOGUE

All 7 Agent Module tools

FINANCIAL 2 tools

Financial join_waitlist Register for a paid vertical waitlist. Inaugural cohort: $19/mo, 900 members, grandfathered for life. AI Compl Financial submit_referral Log a referral signal. Members earn $1.50/referral (4/cycle max, $6 cap). Credits carry forward. Voluntary, pr

WRITE 3 tools

Write get_trial_key Request a free 24-hour trial key. Unlocks all 4 content layers on the chosen vertical. 500-call cap. No paymen Write register_interest Register demand for an unbuilt vertical. 500 signals triggers build queue activation. Include a contact channe Write submit_pov Submit a Proof of Value assessment after exploring the AI Compliance trial. Includes quality scoring and subsc

READ 2 tools

Read check_status Check Agent Module API operational status, version, cohort counts, and seat availability. Read query_knowledge Retrieve structured knowledge from Agent Module verticals. Returns deterministic, validated knowledge nodes. I

FAQ

Questions about Agent Module

Can an AI agent move money through the Agent Module MCP server? +

Yes. The Agent Module server exposes 2 financial tools including join_waitlist, submit_referral. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Agent Module? +

The Agent Module server has 3 write tools including get_trial_key, register_interest, submit_pov. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Agent Module.

How many tools does the Agent Module MCP server expose? +

7 tools across 2 categories: Read, Write. 2 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Agent Module? +

Register the Agent Module MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Agent Module tool call.

Deterministic rules across all 7 Agent Module tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON AGENT MODULE →

Instant setup, no code required.

7 Agent Module tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Agent Module's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →