get_trial_key

Request a free 24-hour trial key. Unlocks all 4 content layers on the chosen vertical. 500-call cap. No payment required.

SERVERAgent Module SOURCEhttps://api.agent-module.dev/mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-agent-module-mcp/get-trial-key.md

WHAT IT DOES

What get_trial_key does on Agent Module

AI agents use get_trial_key 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
`agent_id`	string	Yes	Stable identifier for your agent.
`vertical`	string	—	Which vertical to trial. Defaults to ethics if omitted.

Parameters from the server's own tool schema.

RISK

Why get_trial_key is rated Medium

This tool creates a new trial key (a provisioned resource) associated with the requester, which is a Write operation. It has no financial obligation ('No payment required'), no code execution, and no destructive effect. Misuse risk is low — the worst case is generating spurious trial keys, which is reversible and low-impact given the 500-call cap and 24-hour expiry.

From the tool's definition Request a free 24-hour trial key... No payment required

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_trial_key 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 get_trial_key, this is the rule to start with:

get_trial_key Rate-limited

get_trial_key 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_trial_key": {
      "limits": [
        {
          "counter": "get_trial_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agent Module, apply this rule, and every get_trial_key call is checked against it from then on.

FAQ

Questions about get_trial_key

What does the get_trial_key tool do? +

Request a free 24-hour trial key. Unlocks all 4 content layers on the chosen vertical. 500-call cap. No payment required. 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.

What parameters does get_trial_key accept? +

get_trial_key accepts 2 parameters: agent_id, vertical. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_trial_key? +

Register the Agent Module MCP server in PolicyLayer and add a rule for get_trial_key: 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.

What risk level is get_trial_key? +

get_trial_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit get_trial_key? +

Yes. Add a rate_limit block to the get_trial_key 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.

How do I block get_trial_key completely? +

Set action: deny in the PolicyLayer policy for get_trial_key. 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.

What MCP server provides get_trial_key? +

get_trial_key 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.

KEEP EXPLORING

More on Agent Module, and thousands of servers like it.

This server

All 7 Agent Module tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →