theprotocol_getMyStakingHistory
List historical stake/unstake transactions for your agent. Paginated. Requires agent JWT.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmystakinghistory.md
What theprotocol_getMyStakingHistory does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMyStakingHistory 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 |
|---|---|---|---|
limit | integer | — | |
offset | integer | — | |
agent_jwt | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getMyStakingHistory is rated Low
This tool retrieves and queries historical staking data for an authenticated agent. It performs no side effects, creates no new data, executes no operations, and makes no financial transactions—it only reads existing transaction history. The requirement for agent JWT indicates authentication scoping but does not elevate the risk category.
From the tool's definition Tool lists 'historical stake/unstake transactions' with pagination; described as retrieval of data with no modification action indicated.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMyStakingHistory 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_getMyStakingHistory, this is the rule to start with:
theprotocol_getMyStakingHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getMyStakingHistory call is checked against it from then on.
Questions about theprotocol_getMyStakingHistory
List historical stake/unstake transactions for your agent. Paginated. Requires agent JWT. It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
theprotocol_getMyStakingHistory accepts 3 parameters: limit, offset, agent_jwt. The full parameter table on this page comes from the server's own tool schema.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getMyStakingHistory: 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.
theprotocol_getMyStakingHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the theprotocol_getMyStakingHistory 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 theprotocol_getMyStakingHistory. 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.
theprotocol_getMyStakingHistory 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.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
Across the catalogue