Low Risk

get_court_directory

裁判所の管轄・連絡先情報を取得. Look up a Japanese district court (本庁 or 支部) by code.

Part of the 不動産競売 構造化データハブ — Japan real-estate auctions server.

get_court_directory is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE 不動産競売 構造化データハブ — JAPAN REAL-ESTATE AUCTIONS →

Free to start. No card required.

AI agents call get_court_directory to retrieve information from 不動産競売 構造化データハブ — Japan real-estate auctions without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_court_directory only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_court_directory": {}
  }
}

See the full 不動産競売 構造化データハブ — Japan real-estate auctions policy for all 5 tools.

Get this rule live on your own 不動産競売 構造化データハブ — Japan real-estate auctions server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY 不動産競売 構造化データハブ — JAPAN REAL-ESTATE AUCTIONS →

These attack patterns abuse exactly the kind of access get_court_directory gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_court_directory only ever does what you allow.

SECURE 不動産競売 構造化データハブ — JAPAN REAL-ESTATE AUCTIONS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_court_directory tool do? +

裁判所の管轄・連絡先情報を取得. Look up a Japanese district court (本庁 or 支部) by code.. It is categorised as a Read tool in the 不動産競売 構造化データハブ — Japan real-estate auctions MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_court_directory? +

Register the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server in PolicyLayer and add a rule for get_court_directory: 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 不動産競売 構造化データハブ — Japan real-estate auctions. Nothing to install.

What risk level is get_court_directory? +

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

Can I rate-limit get_court_directory? +

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

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

get_court_directory is provided by the 不動産競売 構造化データハブ — Japan real-estate auctions MCP server (https://keibai-hub.com/mcp-auctions). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 不動産競売 構造化データハブ — Japan real-estate auctions tool call.

Deterministic rules across all 5 不動産競売 構造化データハブ — Japan real-estate auctions tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.