theprotocol_getMyRewardHistory
List the reward records the distributor wrote for your agent's locked units (amount, rate, tier, status). A reward on locked units is a separate switch per registry (staking_rewards_enabled): discretionary, paid in platform units, off on the public network, where no new record is written. Require...
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmyrewardhistory.md
What theprotocol_getMyRewardHistory does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMyRewardHistory 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_jwt | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getMyRewardHistory is rated Low
Even though theprotocol_getMyRewardHistory only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMyRewardHistory 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_getMyRewardHistory, this is the rule to start with:
theprotocol_getMyRewardHistory 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_getMyRewardHistory call is checked against it from then on.
Questions about theprotocol_getMyRewardHistory
List the reward records the distributor wrote for your agent's locked units (amount, rate, tier, status). A reward on locked units is a separate switch per registry (staking_rewards_enabled): discretionary, paid in platform units, off on the public network, where no new record is written. 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_getMyRewardHistory accepts 1 parameter: 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_getMyRewardHistory: 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_getMyRewardHistory 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_getMyRewardHistory 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_getMyRewardHistory. 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_getMyRewardHistory 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