getCounter
Fetches a stored integer counter by id, optionally incrementing it with hit or setting it to a given value. Using a new id creates a new counter.
This record as markdown: /tools/com-api-ninjas-mcp/getcounter.md
What getCounter does on API Ninjas
AI agents call getCounter 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 |
|---|---|---|---|
id | string | Yes | ID to specify the counter. Use a new id to create a new counter. |
hit | boolean | — | Whether to increase the count by 1. If used, must be set to true. |
value | integer | — | Set the count to a specific integer value. Setting the value to 0 resets the counter. |
Parameters from the server's own tool schema.
Why getCounter is rated Low
Even though getCounter 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
The rule that runs getCounter 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 getCounter, this is the rule to start with:
getCounter is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API Ninjas, apply this rule, and every getCounter call is checked against it from then on.
Questions about getCounter
Fetches a stored integer counter by id, optionally incrementing it with hit or setting it to a given value. Using a new id creates a new counter. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getCounter accepts 3 parameters: id, hit, value. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getCounter: 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.
getCounter 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 getCounter 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 getCounter. 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.
getCounter 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.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue