filter_points_by_radius

A read tool on the CLIO Adios MCP server.

SERVERCLIO Adios SOURCEpypi:clio-kit

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/filter-points-by-radius.md

WHAT IT DOES

What filter_points_by_radius does on CLIO Adios

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

RISK

Why filter_points_by_radius is rated Low

The tool name implies selecting or retrieving a subset of points based on spatial criteria (radius-based filtering), which is a read operation with no side effects. The lack of mutating keywords ('create', 'delete', 'update', 'execute') and the analytical nature of the server suggest data retrieval.

From the tool's definition Tool name 'filter_points_by_radius' suggests a filtering/query operation on spatial data. Description is empty, limiting direct evidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs filter_points_by_radius safely

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

filter_points_by_radius Allowed

filter_points_by_radius 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": {
    "filter_points_by_radius": {}
  }
}

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

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

FAQ

Questions about filter_points_by_radius

What does the filter_points_by_radius tool do? +

filter_points_by_radius is a read tool on the CLIO Adios MCP server. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on filter_points_by_radius? +

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

What risk level is filter_points_by_radius? +

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

Can I rate-limit filter_points_by_radius? +

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

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

filter_points_by_radius is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools →

Across the catalogue

The MCP Attack Database →

Guides

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