replace_dataset_log · Respan MCP Server MCP: Risk & Policy

WHAT IT DOES

What replace_dataset_log does on Respan MCP Server

AI agents use replace_dataset_log to create or update resources in Respan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Respan MCP Server environment.

WHY IT NEEDS A POLICY

Why replace_dataset_log needs a policy

This tool modifies existing data within a dataset by fully overwriting log records. While 'overwrite' could suggest destructive intent, the operation is reversible (a previous version can be restored, and this is a write operation on monitoring/logging infrastructure rather than permanent deletion).

From the tool's definition The tool description explicitly states 'Replace (full overwrite) a log in a dataset. Updates input, output, expected_output, and/or metadata fields.' The action overwrites existing log entries, which modifies data in place.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

replace_dataset_log Rate-limited

replace_dataset_log stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "replace_dataset_log": {
      "limits": [
        {
          "counter": "replace_dataset_log_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about replace_dataset_log

What does the replace_dataset_log tool do? +

Replace (full overwrite) a log in a dataset. Updates input, output, expected_output, and/or metadata fields. It is categorised as a Write tool in the Respan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on replace_dataset_log? +

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

What risk level is replace_dataset_log? +

replace_dataset_log is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit replace_dataset_log? +

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

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

replace_dataset_log is provided by the Respan MCP Server MCP server (respanai/respan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.