2_get_indicators
AI agents call 2_get_indicators to retrieve information from MoSPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is part of an MCP server designed to query statistical and demographic data from a government API. The naming pattern and workflow position (step 2 in a 4-step process, after 'know_about_mospi_api' and before 'get_metadata' and 'get_data') strongly suggest this retrieves a list or catalog of available indicators without modifying data. No execution, deletion, or financial operations are implied.
From the tool's definition Tool name '2_get_indicators' and position in a 4-tool workflow for 'accessing India's Ministry of Statistics and Programme Implementation (MoSPI) data APIs' suggests data retrieval. Sibling tools include 'get_metadata' and 'get_data', both Read operations.
Attacks that exploit this kind of access
2_get_indicators. It is categorised as a Read tool in the MoSPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MoSPI MCP Server MCP server in PolicyLayer and add a rule for 2_get_indicators: 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 MoSPI MCP Server. Nothing to install.
2_get_indicators 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 2_get_indicators 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 2_get_indicators. 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.
2_get_indicators is provided by the MoSPI MCP Server MCP server (mayankthekumawat/mospi-mcp-api). 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 →