run_spi_table · DMAP-AI MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_spi_table does on DMAP-AI MCP Server

AI agents invoke run_spi_table to trigger actions in DMAP-AI MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_spi_table needs a policy

The 'run_' prefix pattern is consistent with all sibling tools on this server (run_drought_periodicity_analysis, run_drought_severity_events, run_wavelet_scalogram), which are all execution-type tools that trigger analyses. 'run_spi_table' likely executes an SPI (Standardized Precipitation Index) computation and generates a results table using external data sources (NASA POWER or ERA5-Land/CDS).

From the tool's definition Tool name 'run_spi_table' and server context 'drought monitoring and SPI drought analysis using NASA POWER and ERA5-Land/CDS data'; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_spi_table Rate-limited

run_spi_table stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_spi_table": {
      "limits": [
        {
          "counter": "run_spi_table_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DMAP-AI MCP Server, so you can run agents against it safely.

FAQ

Questions about run_spi_table

What does the run_spi_table tool do? +

run_spi_table. It is categorised as a Execute tool in the DMAP-AI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_spi_table? +

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

What risk level is run_spi_table? +

run_spi_table is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_spi_table? +

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

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

run_spi_table is provided by the DMAP-AI MCP Server MCP server (sohrab4748/dmap-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.