1_know_about_mospi_api
AI agents call 1_know_about_mospi_api 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.
This tool appears to serve a documentation or discovery function—providing information about the MoSPI API structure, available endpoints, or capabilities. Such functions are Read category (retrieves information with no side effects).
From the tool's definition Tool name '1_know_about_mospi_api' suggests information retrieval about the MoSPI API itself. No description provided, but the naming convention (prefix '1_') and position in a 4-tool workflow (2_get_indicators, 3_get_metadata, 4_get_data) indicates this is a…
Attacks that exploit this kind of access
1_know_about_mospi_api. 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 1_know_about_mospi_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 MoSPI MCP Server. Nothing to install.
1_know_about_mospi_api 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 1_know_about_mospi_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 1_know_about_mospi_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.
1_know_about_mospi_api 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 →