Return the jpzip dataset metadata: data version (YYYY-MM), generated timestamp, total entry count, and per-prefecture counts. Useful for confirming the dataset is current.
AI agents call get_metadata to retrieve information from jpzip MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries metadata about the jpzip dataset without modifying, executing operations, or deleting data. It is a read-only informational lookup, classified as Read with low severity since exposure of dataset version and count information poses minimal risk to an AI agent.
From the tool's definition Tool name 'get_metadata' and description state it 'Return[s] the jpzip dataset metadata' including 'data version', 'generated timestamp', 'total entry count', and 'per-prefecture counts'. This is purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
Return the jpzip dataset metadata: data version (YYYY-MM), generated timestamp, total entry count, and per-prefecture counts. Useful for confirming the dataset is current. It is categorised as a Read tool in the jpzip MCP server MCP Server, which means it retrieves data without modifying state.
Register the jpzip MCP server MCP server in PolicyLayer and add a rule for 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 jpzip MCP server. Nothing to install.
get_metadata 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 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.
Set action: deny in the PolicyLayer policy for 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.
get_metadata is provided by the jpzip MCP server MCP server (jpzip/mcp). 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 →