import_temporal_state · KafkaIQ MCP: Risk & Policy

WHAT IT DOES

What import_temporal_state does on KafkaIQ

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

WHY IT NEEDS A POLICY

Why import_temporal_state needs a policy

Importing state from a file modifies the internal temporal state of the KafkaIQ system but is reversible (can be overwritten or cleared via clear_temporal_memory). It does not delete data (Destructive), execute arbitrary operations (Execute), or involve financial transactions (Financial).

From the tool's definition The tool name 'import_temporal_state' and description 'Import previously exported temporal memory from a JSON file' indicate it loads and applies saved state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_temporal_state Rate-limited

import_temporal_state 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": {
    "import_temporal_state": {
      "limits": [
        {
          "counter": "import_temporal_state_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 KafkaIQ, so you can run agents against it safely.

FAQ

Questions about import_temporal_state

What does the import_temporal_state tool do? +

Import previously exported temporal memory from a JSON file. It is categorised as a Write tool in the KafkaIQ MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_temporal_state? +

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

What risk level is import_temporal_state? +

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

Can I rate-limit import_temporal_state? +

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

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

import_temporal_state is provided by the KafkaIQ MCP server (ojhaayush03/kafka_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.