Low Risk

get_da

Get a full DA record by name (exact or close partial match).

Part of the California Justice Watch server.

get_da 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 CALIFORNIA JUSTICE WATCH →

Free to start. No card required.

AI agents call get_da to retrieve information from California Justice Watch 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_da 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_da": {}
  }
}

See the full California Justice Watch policy for all 15 tools.

Get this rule live on your own California Justice Watch server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CALIFORNIA JUSTICE WATCH →

View all 15 tools →

These attack patterns abuse exactly the kind of access get_da 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_da only ever does what you allow.

SECURE CALIFORNIA JUSTICE WATCH →

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

What does the get_da tool do? +

Get a full DA record by name (exact or close partial match).. It is categorised as a Read tool in the California Justice Watch MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_da? +

Register the California Justice Watch MCP server in PolicyLayer and add a rule for get_da: 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 California Justice Watch. Nothing to install.

What risk level is get_da? +

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

Can I rate-limit get_da? +

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

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

get_da is provided by the California Justice Watch MCP server (https://cajusticewatch.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every California Justice Watch tool call.

Deterministic rules across all 15 California Justice Watch 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.