Low Risk

spatial_heat

v3.1.0 M4: Top-K most-touched files in a time window by

How to control spatial_heat ↓

What spatial_heat does on Codevira MCP

AI agents call spatial_heat to retrieve information from Codevira MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why spatial_heat needs a policy

This tool queries historical file access patterns within a specified time window and returns ranked results. It performs analysis and retrieval of existing data without creating, modifying, deleting, or executing any operations.

From the tool's definition Tool name 'spatial_heat' with description indicating it retrieves 'Top-K most-touched files in a time window' — a data retrieval/query operation with no modification or deletion capability.

Documented attack patterns abuse exactly the kind of access spatial_heat gives an agent:

How to control spatial_heat

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "spatial_heat": {}
  }
}

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

  1. Create a free account and register Codevira MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about spatial_heat

What does the spatial_heat tool do? +

v3.1.0 M4: Top-K most-touched files in a time window by. It is categorised as a Read tool in the Codevira MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spatial_heat? +

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

What risk level is spatial_heat? +

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

Can I rate-limit spatial_heat? +

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

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

spatial_heat is provided by the Codevira MCP server (sachinshelke/codevira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codevira MCP tool call.

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

Free to start. No card required.

48 Codevira MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.