sap_perpspad_get_token_events
Fetch buyback / burn / fee transaction events for one PerpsPad token (its backing perp PnL drives buybacks and burns). Optional kind filter (comma-separated: buyback, external_buyback, burn, claim, creator_payout; default buyback+external_buyback+burn) and paging. Free read. SAP MCP execution gui...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-perpspad-get-token-events.md
What sap_perpspad_get_token_events does on Sap
AI agents call sap_perpspad_get_token_events to retrieve information from Sap 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 |
|---|---|---|---|
id | string | Yes | Token UUID or mint address |
kind | string | — | Comma-separated event kinds filter (e.g. "buyback,burn") |
limit | number | — | Max events per page |
offset | number | — | Pagination offset |
Parameters from the server's own tool schema.
Why sap_perpspad_get_token_events is rated Low
Tool queries historical token events with optional filtering and pagination, pure data retrieval with no state modifications.
From the tool's definition Fetch transaction events; free read; no side effects.
Attacks that exploit this kind of access
The rule that runs sap_perpspad_get_token_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_perpspad_get_token_events, this is the rule to start with:
sap_perpspad_get_token_events 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 Sap, apply this rule, and every sap_perpspad_get_token_events call is checked against it from then on.
Questions about sap_perpspad_get_token_events
Fetch buyback / burn / fee transaction events for one PerpsPad token (its backing perp PnL drives buybacks and burns). Optional kind filter (comma-separated: buyback, external_buyback, burn, claim, creator_payout; default buyback+external_buyback+burn) and paging. Free read. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_perpspad_get_token_events accepts 4 parameters: id, kind, limit, offset. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_perpspad_get_token_events: 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 Sap. Nothing to install.
sap_perpspad_get_token_events 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 sap_perpspad_get_token_events 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 sap_perpspad_get_token_events. 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.
sap_perpspad_get_token_events is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue