List available datasets from Utsunomiya city.
AI agents call list_datasets to retrieve information from Utsunomiya without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about available datasets. It does not create, modify, delete, or execute any operations—it merely queries and returns a list of dataset metadata. This is a standard Read category operation with minimal risk, as the worst outcome of misuse would be information disclosure about what datasets exist, which is typically public metadata in open data contexts.
From the tool's definition Tool name 'list_datasets' and description 'List available datasets' indicates retrieval of metadata without modification. The function lists or enumerates available datasets, a pure read operation with no side effects.
Attacks that exploit this kind of access
List available datasets from Utsunomiya city. It is categorised as a Read tool in the Utsunomiya MCP Server, which means it retrieves data without modifying state.
Register the Utsunomiya MCP server in PolicyLayer and add a rule for list_datasets: 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 Utsunomiya. Nothing to install.
list_datasets 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 list_datasets 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 list_datasets. 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.
list_datasets is provided by the Utsunomiya MCP server (takurot/utsunomiya-mcp-server). 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 →