Low Risk

fillin_stats

Get corpus stats — total docs, date range, freshness.

Part of the Fillin server.

fillin_stats 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 FILLIN →

Free to start. No card required.

AI agents call fillin_stats to retrieve information from Fillin 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 fillin_stats 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": {
    "fillin_stats": {}
  }
}

See the full Fillin policy for all 11 tools.

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

ENFORCE ON MY FILLIN →

View all 11 tools →

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

SECURE FILLIN →

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

What does the fillin_stats tool do? +

Get corpus stats — total docs, date range, freshness.. It is categorised as a Read tool in the Fillin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fillin_stats? +

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

What risk level is fillin_stats? +

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

Can I rate-limit fillin_stats? +

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

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

fillin_stats is provided by the Fillin MCP server (https://fillin.glyphapi.dev/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fillin tool call.

Deterministic rules across all 11 Fillin 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.