discussion_archive · Lockstep MCP: Risk & Policy

WHAT IT DOES

What discussion_archive does on Lockstep

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

WHY IT NEEDS A POLICY

Why discussion_archive needs a policy

This tool modifies data (changes discussion status to archived) but the change is reversible and non-destructive. While the description mentions 'Archived discussions can be deleted later,' this refers to a future potential action, not an action this tool performs. The immediate effect is a metadata/state modification of a discussion record, classifying it as Write rather than Destructive.

From the tool's definition Tool description states it 'Archive[s] a resolved discussion.' Archiving is a state-change operation that modifies the status of a discussion record from active to archived, which is reversible (discussions can be unarchived in typical systems).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

discussion_archive Rate-limited

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

FAQ

Questions about discussion_archive

What does the discussion_archive tool do? +

Archive a resolved discussion. Archived discussions can be deleted later. It is categorised as a Write tool in the Lockstep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on discussion_archive? +

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

What risk level is discussion_archive? +

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

Can I rate-limit discussion_archive? +

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

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

discussion_archive is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.