Calls a Nodit Aptos Indexer API. Returns the API response. Before making the call, it's recommended to verify the detailed API specifications using the 'get_nodit_aptos_indexer_api_spec' tool. Please note that using this tool will consume your API quota.
AI agents invoke call_nodit_aptos_indexer_api to trigger actions in Nodit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
network | string | Yes | Nodit network to call. e.g. 'mainnet' or 'testnet'. |
requestBody | object | Yes | Graphql request body matching the API's spec. |
Parameters from the server's own tool schema.
The tool executes an external API call to the Nodit Aptos Indexer service. While it appears to be primarily a read/query operation (indexer APIs typically retrieve blockchain data), it triggers an external operation with real-world side effects (quota consumption) and the exact behavior depends on arguments. This places it in Execute rather than Read.
From the tool's definition 'Calls a Nodit Aptos Indexer API. Returns the API response.' and 'using this tool will consume your API quota'
Attacks that exploit this kind of access
Calls a Nodit Aptos Indexer API. Returns the API response. Before making the call, it's recommended to verify the detailed API specifications using the 'get_nodit_aptos_indexer_api_spec' tool. Please note that using this tool will consume your API quota. It is categorised as a Execute tool in the Nodit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
call_nodit_aptos_indexer_api accepts 2 parameters: network, requestBody. Required: network, requestBody. The full parameter table on this page comes from the server's own tool schema.
Register the Nodit MCP server in PolicyLayer and add a rule for call_nodit_aptos_indexer_api: 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 Nodit. Nothing to install.
call_nodit_aptos_indexer_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_nodit_aptos_indexer_api 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 call_nodit_aptos_indexer_api. 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.
call_nodit_aptos_indexer_api is provided by the Nodit MCP server (@noditlabs/nodit-mcp-server). 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 →