Get the total count of available rejection messages (currently 1,021 different ways to say no)
Part of the No As Service MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call getNoCount to retrieve information from No As Service 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 getNoCount 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.
tools:
getNoCount:
rules:
- action: allowSee the full No As Service policy for all 2 tools.
Agents calling read-class tools like getNoCount have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get the total count of available rejection messages (currently 1,021 different ways to say no). It is categorised as a Read tool in the No As Service MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for getNoCount. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the No As Service MCP server.
getNoCount 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 getNoCount rule in your Intercept 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 Intercept policy for getNoCount. 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.
getNoCount is provided by the No As Service MCP server (no-as-service). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept