build_timeline · SIFTGuard MCP: Risk & Policy

WHAT IT DOES

What build_timeline does on SIFTGuard

AI agents invoke build_timeline to trigger actions in SIFTGuard. 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 build_timeline needs a policy

This tool actively processes and correlates multiple evidence sources (memory, logs, disk artifacts) from a directory to produce a unified timeline. It triggers external forensic operations across multiple data types, making it an Execute-category tool.

From the tool's definition 'Build a supertimeline from all evidence in a directory. Correlates memory, logs, disk artifacts chronologically.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_timeline Rate-limited

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

FAQ

Questions about build_timeline

What does the build_timeline tool do? +

Build a supertimeline from all evidence in a directory. Correlates memory, logs, disk artifacts chronologically. It is categorised as a Execute tool in the SIFTGuard MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_timeline? +

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

What risk level is build_timeline? +

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

Can I rate-limit build_timeline? +

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

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

build_timeline is provided by the SIFTGuard MCP server (sodiq-code/siftguard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.