Get current transactions per second on Solana
AI agents call GET_TPS to retrieve information from Solana MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a network statistic (transactions per second) from the Solana blockchain. It is a read-only query with no ability to modify data, execute code, trigger external operations, or affect financial state. The low severity reflects minimal risk even if queried repeatedly by an AI agent, as the operation has no side effects and returns public blockchain information.
From the tool's definition Tool name 'GET_TPS' and description 'Get current transactions per second on Solana' indicate a data retrieval operation that queries the current network metric without modifying, executing code, or causing side effects.
Attacks that exploit this kind of access
Get current transactions per second on Solana. It is categorised as a Read tool in the Solana MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Solana MCP Server MCP server in PolicyLayer and add a rule for GET_TPS: 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 Solana MCP Server. Nothing to install.
GET_TPS 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 GET_TPS 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 GET_TPS. 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.
GET_TPS is provided by the Solana MCP Server MCP server (pingaifun/ping-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →