theprotocol_getAgentStakingHistory

TEG-side stake/unstake history for one of your agents.

SERVERTheProtocol — Sovereign AI Agent Platform SOURCEhttps://api.theprotocol.cloud/mcp/sse

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getagentstakinghistory.md

WHAT IT DOES

What theprotocol_getAgentStakingHistory does on TheProtocol — Sovereign AI Agent Platform

AI agents call theprotocol_getAgentStakingHistory to retrieve information from TheProtocol — Sovereign AI Agent Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`agent_did`	string	Yes

Parameters from the server's own tool schema.

RISK

Why theprotocol_getAgentStakingHistory is rated Low

This tool queries past staking transactions for an agent without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, posing minimal risk even if accessed by an AI agent.

From the tool's definition Tool description states it retrieves 'stake/unstake history' — a historical query operation with no modification or side effects. The verb 'get' and word 'history' indicate data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs theprotocol_getAgentStakingHistory safely

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

theprotocol_getAgentStakingHistory Allowed

theprotocol_getAgentStakingHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "theprotocol_getAgentStakingHistory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getAgentStakingHistory call is checked against it from then on.

FAQ

Questions about theprotocol_getAgentStakingHistory

What does the theprotocol_getAgentStakingHistory tool do? +

TEG-side stake/unstake history for one of your agents. It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.

What parameters does theprotocol_getAgentStakingHistory accept? +

theprotocol_getAgentStakingHistory accepts 1 parameter: agent_did. Required: agent_did. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_getAgentStakingHistory? +

Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getAgentStakingHistory: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.

What risk level is theprotocol_getAgentStakingHistory? +

theprotocol_getAgentStakingHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit theprotocol_getAgentStakingHistory? +

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

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

theprotocol_getAgentStakingHistory is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.

This server

All 413 TheProtocol — Sovereign AI Agent Platform tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →