Low Risk

get_state_filing_status

List the employer's state agency account numbers (last-four only) per (state, registration_type) tuple — UC, withholding, SDI. Returns the agency name and a registration URL for any that are missing. Use before generating quarterly filing instructions (e.g., 'file Form UC-2 for Q2 — your PA UC ac...

Part of the Nannykeeper server.

get_state_filing_status 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 NANNYKEEPER →

Free to start. No card required.

AI agents call get_state_filing_status to retrieve information from Nannykeeper 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_state_filing_status 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_state_filing_status": {}
  }
}

See the full Nannykeeper policy for all 5 tools.

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

ENFORCE ON MY NANNYKEEPER →

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

SECURE NANNYKEEPER →

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

What does the get_state_filing_status tool do? +

List the employer's state agency account numbers (last-four only) per (state, registration_type) tuple — UC, withholding, SDI. Returns the agency name and a registration URL for any that are missing. Use before generating quarterly filing instructions (e.g., 'file Form UC-2 for Q2 — your PA UC account is ••••5678') or when a customer asks whether their state setup is complete. Read-only. To update, use the POST /api/v1/state-registrations REST endpoint or direct the customer to /settings/states — LLMs shouldn't fabricate account numbers since they land on real tax filings.. It is categorised as a Read tool in the Nannykeeper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_state_filing_status? +

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

What risk level is get_state_filing_status? +

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

Can I rate-limit get_state_filing_status? +

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

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

get_state_filing_status is provided by the Nannykeeper MCP server (@nannykeeper/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nannykeeper tool call.

Deterministic rules across all 5 Nannykeeper 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.