getCounty

Returns details for one or more counties matching the input parameters.

SERVERAPI Ninjas SOURCEhttps://mcp.api-ninjas.com/mcp

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-api-ninjas-mcp/getcounty.md

WHAT IT DOES

What getCounty does on API Ninjas

AI agents call getCounty to retrieve information from API Ninjas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`limit`	integer	—	Number of results to return. Must be between 1 and 30. Default is 1.
`state`	string	—	2-letter state code (case-insensitive).
`county`	string	—	Full name of the county to search.
`offset`	integer	—	Number of results to offset for pagination. Default is 0.
`zipcode`	string	—	5-digit ZIP code to search.

Parameters from the server's own tool schema.

RISK

Why getCounty is rated Low

Even though getCounty only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getCounty safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCounty, this is the rule to start with:

getCounty Allowed

getCounty is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getCounty": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API Ninjas, apply this rule, and every getCounty call is checked against it from then on.

FAQ

Questions about getCounty

What does the getCounty tool do? +

Returns details for one or more counties matching the input parameters. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.

What parameters does getCounty accept? +

getCounty accepts 5 parameters: limit, state, county, offset, zipcode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getCounty? +

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

What risk level is getCounty? +

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

Can I rate-limit getCounty? +

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

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

getCounty is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API Ninjas, and thousands of servers like it.

This server

All 244 API Ninjas tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →