AI agents call get-soon-mainnet-last-transaction to retrieve information from SVM-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data from a blockchain without any capability to modify, execute, or delete data. It is a simple query operation that returns information about past transactions. The read-only nature and lack of side effects place it firmly in the Read category with low severity, as misuse would only expose existing blockchain data without causing harm.
From the tool's definition Tool name 'get-soon-mainnet-last-transaction' and description 'Get the last transaction of an address on the Soon mainnet' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
Get the last transaction of an address on the Soon mainnet. It is categorised as a Read tool in the SVM-MCP MCP Server, which means it retrieves data without modifying state.
Register the SVM- MCP server in PolicyLayer and add a rule for get-soon-mainnet-last-transaction: 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 SVM-MCP. Nothing to install.
get-soon-mainnet-last-transaction 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-soon-mainnet-last-transaction 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-soon-mainnet-last-transaction. 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-soon-mainnet-last-transaction is provided by the SVM- MCP server (rkmonarch/svm-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 →