sap_perpspad_get_tokens
List PerpsPad launched tokens: ticker, name, mint, backing perp (underlying, leverage, direction), quote token, SOL raised, migration status, pool addresses. Sort: newest (default), oldest, or raised (most SOL raised first). Free read. SAP MCP execution guidance: Intent: read/discovery workflow. ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-perpspad-get-tokens.md
What sap_perpspad_get_tokens does on Sap
AI agents call sap_perpspad_get_tokens 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 |
|---|---|---|---|
sort | string | — | Sort order |
limit | number | — | Max tokens per page |
offset | number | — | Pagination offset |
Parameters from the server's own tool schema.
Why sap_perpspad_get_tokens is rated Low
Tool queries and lists token metadata with no side effects or state modifications.
From the tool's definition List PerpsPad launched tokens, free read, sort options, discovery workflow
Attacks that exploit this kind of access
The rule that runs sap_perpspad_get_tokens 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_tokens, this is the rule to start with:
sap_perpspad_get_tokens 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_tokens call is checked against it from then on.
Questions about sap_perpspad_get_tokens
List PerpsPad launched tokens: ticker, name, mint, backing perp (underlying, leverage, direction), quote token, SOL raised, migration status, pool addresses. Sort: newest (default), oldest, or raised (most SOL raised first). 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_tokens accepts 3 parameters: sort, limit, offset. 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_tokens: 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_tokens 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_tokens 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_tokens. 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_tokens 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