get_nodit_aptos_indexer_api_spec

Returns the GraphQL specification for a specific query root in the Nodit Aptos Indexer API.

Server Nodit @noditlabs/nodit-mcp-server
Category Read
Risk class Low
Parameters 11 required

What get_nodit_aptos_indexer_api_spec does on Nodit

AI agents call get_nodit_aptos_indexer_api_spec to retrieve information from Nodit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
queryRoot string Yes The name of the query root to get the specification for. Use list_nodit_aptos_indexer_api_query_root to see available query roots.

Parameters from the server's own tool schema.

Why get_nodit_aptos_indexer_api_spec needs a policy

This is a purely informational read operation that retrieves API schema metadata. It does not execute queries, modify data, delete resources, or commit financial transactions. The blast radius of misuse is minimal—an agent could only spam requests or gather reconnaissance information about available API capabilities.

From the tool's definition Tool name and description indicate it 'Returns the GraphQL specification' — a retrieval operation with no side effects. The action is to fetch and display API schema/specification documentation.

Risk signalsAdmin/system-level operation

Questions about get_nodit_aptos_indexer_api_spec

What does the get_nodit_aptos_indexer_api_spec tool do? +

Returns the GraphQL specification for a specific query root in the Nodit Aptos Indexer API. It is categorised as a Read tool in the Nodit MCP Server, which means it retrieves data without modifying state.

What parameters does get_nodit_aptos_indexer_api_spec accept? +

get_nodit_aptos_indexer_api_spec accepts 1 parameter: queryRoot. Required: queryRoot. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_nodit_aptos_indexer_api_spec? +

Register the Nodit MCP server in PolicyLayer and add a rule for get_nodit_aptos_indexer_api_spec: 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.

What risk level is get_nodit_aptos_indexer_api_spec? +

get_nodit_aptos_indexer_api_spec is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_nodit_aptos_indexer_api_spec? +

Yes. Add a rate_limit block to the get_nodit_aptos_indexer_api_spec 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.

How do I block get_nodit_aptos_indexer_api_spec completely? +

Set action: deny in the PolicyLayer policy for get_nodit_aptos_indexer_api_spec. 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.

What MCP server provides get_nodit_aptos_indexer_api_spec? +

get_nodit_aptos_indexer_api_spec 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.