Get recent (last 5) transactions for an address. Remember its an EVM chain but the token is $IP
AI agents call get_transactions to retrieve information from Story SDK 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 historical transaction data without creating, modifying, or deleting any resources. The query-only nature and read-only pattern clearly indicates a Read category classification.
From the tool's definition Tool description states it 'Get[s] recent (last 5) transactions for an address' — a pure retrieval operation with no side effects or modifications to data.
Documented attack patterns abuse exactly the kind of access get_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Story SDK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_transactions": {}
}
}get_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get recent (last 5) transactions for an address. Remember its an EVM chain but the token is $IP. It is categorised as a Read tool in the Story SDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Story SDK MCP Server MCP server in PolicyLayer and add a rule for get_transactions: 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 Story SDK MCP Server. Nothing to install.
get_transactions 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_transactions 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_transactions. 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_transactions is provided by the Story SDK MCP Server MCP server (piplabs/story-mcp-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Story SDK MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Story SDK MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.