recorded_history

A write tool on the Tolpo MCP server.

SERVERTolpo SOURCEsignerless/tolpo

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tolpo/recorded-history.md

WHAT IT DOES

What recorded_history does on Tolpo

AI agents use recorded_history to create or update resources in Tolpo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tolpo environment.

RISK

Why recorded_history is rated Medium

An AI agent can call recorded_history faster than any human can review: one bad instruction and it creates or modifies resources in Tolpo by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs recorded_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tolpo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recorded_history, this is the rule to start with:

recorded_history Rate-limited

recorded_history 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": {
    "recorded_history": {
      "limits": [
        {
          "counter": "recorded_history_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 Tolpo, apply this rule, and every recorded_history call is checked against it from then on.

FAQ

Questions about recorded_history

What does the recorded_history tool do? +

recorded_history is a write tool on the Tolpo MCP server. It is categorised as a Write tool in the Tolpo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on recorded_history? +

Register the Tolpo MCP server in PolicyLayer and add a rule for recorded_history: 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 Tolpo. Nothing to install.

What risk level is recorded_history? +

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

Can I rate-limit recorded_history? +

Yes. Add a rate_limit block to the recorded_history 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 recorded_history completely? +

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

recorded_history is provided by the Tolpo MCP server (signerless/tolpo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tolpo, and thousands of servers like it.

This server

All 243 Tolpo tools →

Across the catalogue

The MCP Attack Database →

Guides

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