Retrieve state changes that occurred during a transaction.
AI agents call getTransactionStateChanges to retrieve information from Agentek Eth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only ('Retrieve'). It queries past transaction state changes on the Ethereum blockchain, which is a read-only operation with no side effects, no execution of arbitrary code, and no possibility of modifying or deleting data. The low severity reflects minimal blast radius if misused—an agent could at worst spam queries but cannot cause financial loss or data damage.
From the tool's definition Tool name 'getTransactionStateChanges' and description 'Retrieve state changes that occurred during a transaction' both indicate a query operation that retrieves historical blockchain data without modifying or executing any actions.
Documented attack patterns abuse exactly the kind of access getTransactionStateChanges gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentek Eth, and nothing reaches the server without passing your rules. This is the rule we recommend for getTransactionStateChanges:
{
"version": "1",
"default": "deny",
"tools": {
"getTransactionStateChanges": {}
}
}getTransactionStateChanges 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.
Retrieve state changes that occurred during a transaction. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getTransactionStateChanges: 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 Agentek Eth. Nothing to install.
getTransactionStateChanges 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 getTransactionStateChanges 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 getTransactionStateChanges. 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.
getTransactionStateChanges is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentek Eth, 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.
165 Agentek Eth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.