AI agents use encode_call to create or update resources in Gulltoppr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gulltoppr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
args | array | — | Function arguments, in order. Pass uint values as decimal strings. |
chain | string | Yes | Chain alias ("ethereum", "base", "optimism", "arbitrum", "polygon", "local") or numeric chain id. |
value | string | — | Native value in wei (decimal string), for payable functions. |
address | string | Yes | 0x contract address. |
rpc_url | string | — | Override RPC URL. Required for chains with no default (e.g. local/31337). |
function | string | Yes | Function name, or full signature like "transfer(address,uint256)" if overloaded. |
Parameters from the server's own tool schema.
The tool modifies/prepares data (calldata encoding) that directly enables financial operations. Although encoding alone is reversible and non-destructive, it produces executable transaction instructions that could move funds or alter smart contract state when combined with signing.
From the tool's definition Tool 'encode_call' transforms function calls into calldata format (0x...). While no transaction is sent, this creates encoded transaction data that can be immediately used to construct and execute financial transactions on blockchains.
Attacks that exploit this kind of access
Encode a function call to calldata (0x…) without sending anything. It is categorised as a Write tool in the Gulltoppr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
encode_call accepts 6 parameters: args, chain, value, address, rpc_url, function. Required: chain, address, function. The full parameter table on this page comes from the server's own tool schema.
Register the Gulltoppr MCP server in PolicyLayer and add a rule for encode_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 Gulltoppr. Nothing to install.
encode_call is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the encode_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 encode_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.
encode_call is provided by the Gulltoppr MCP server (https://mcp.gulltoppr.dev/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 →