AI agents call StateChange as a supporting operation in Phalcon workflows.
With no description, classification is speculative. The name 'StateChange' in a blockchain context (alongside tools like BalanceChange, Trace, TransactionOverview) most likely refers to reading/querying state changes from transactions rather than executing or writing them. However, without confirmation, confidence is low. Defaulting to 'Other' given the ambiguity, though 'Read' is plausible.
From the tool's definition Tool name is 'StateChange' but description is empty/uninformative. Sibling tools suggest blockchain/transaction context.
Documented attack patterns abuse exactly the kind of access StateChange gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Phalcon, and nothing reaches the server without passing your rules. This is the rule we recommend for StateChange:
{
"version": "1",
"default": "deny",
"tools": {
"StateChange": {
"limits": [
{
"counter": "statechange_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}StateChange gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
StateChange. It is categorised as a Other tool in the Phalcon MCP Server, which means it performs auxiliary operations.
Register the Phalcon MCP server in PolicyLayer and add a rule for StateChange: 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 Phalcon. Nothing to install.
StateChange is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the StateChange 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 StateChange. 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.
StateChange is provided by the Phalcon MCP server (mark3labs/phalcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Phalcon, 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.
7 Phalcon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.