fast-count

THE RISK

Low Risk

Why fast-count needs a policy

Fast-count performs optimized COUNT aggregation queries on a PostGIS database. COUNT queries are inherently read-only operations that retrieve numerical summaries without side effects. While it executes a query against a database, the operation is non-destructive and returns only statistical information.

From the tool's definition Tool description indicates 'count sorguları' (count queries), which are read operations that retrieve aggregate statistics without modifying data. The term 'optimize edilmiş' (optimized) emphasizes query efficiency rather than data mutation.

Documented attack patterns abuse exactly the kind of access fast-count gives an agent:

POLICY

How to control fast-count

PolicyLayer is an MCP gateway — it sits between your AI agents and PostGIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fast-count:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fast-count": {}
  }
}

fast-count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register PostGIS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about fast-count

What does the fast-count tool do? +

Sayma sorularını hızlı şekilde yanıtlar - optimize edilmiş count sorguları. It is categorised as a Read tool in the PostGIS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fast-count? +

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

What risk level is fast-count? +

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

Can I rate-limit fast-count? +

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

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

fast-count is provided by the PostGIS MCP Server MCP server (receptopalak/postgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PostGIS MCP Server tool call.

Start from PostGIS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →