3_get_metadata

3_get_metadata

Server MoSPI MCP Server mayankthekumawat/mospi-mcp-api
Category Read
Risk class Low
Parameters 00 required

What 3_get_metadata does on MoSPI MCP Server

AI agents call 3_get_metadata 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.

Why 3_get_metadata needs a policy

Based on naming convention and workflow context (part of a data query pipeline alongside 'get_indicators' and 'get_data'), this tool almost certainly retrieves or queries metadata without side effects. The 'get_' prefix and 'metadata' suffix are standard indicators of read operations.

From the tool's definition Tool name '3_get_metadata' and position in a 4-tool MoSPI workflow suggest it retrieves metadata about available indicators.

Questions about 3_get_metadata

What does the 3_get_metadata tool do? +

3_get_metadata. It is categorised as a Read tool in the MoSPI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on 3_get_metadata? +

Register the MoSPI MCP Server MCP server in PolicyLayer and add a rule for 3_get_metadata: 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.

What risk level is 3_get_metadata? +

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

Can I rate-limit 3_get_metadata? +

Yes. Add a rate_limit block to the 3_get_metadata 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 3_get_metadata completely? +

Set action: deny in the PolicyLayer policy for 3_get_metadata. 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 3_get_metadata? +

3_get_metadata 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.

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