call a starknet function without creating a StarkNet transaction
AI agents call starknet_call to retrieve information from Starknet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly states it calls a function 'without creating a StarkNet transaction', meaning it performs a read-only call against the blockchain state with no side effects. This is analogous to an eth_call in Ethereum — it queries contract state without modifying it.
From the tool's definition call a starknet function without creating a StarkNet transaction
Documented attack patterns abuse exactly the kind of access starknet_call gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Starknet MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for starknet_call:
{
"version": "1",
"default": "deny",
"tools": {
"starknet_call": {}
}
} starknet_call 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.
call a starknet function without creating a StarkNet transaction. It is categorised as a Read tool in the Starknet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Starknet MCP Server MCP server in PolicyLayer and add a rule for starknet_call: 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 Starknet MCP Server. Nothing to install.
starknet_call 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 starknet_call 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 starknet_call. 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.
starknet_call is provided by the Starknet MCP Server MCP server (milancermak/starknet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Starknet 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.
21 Starknet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.