discussion_resolve · Lockstep MCP: Risk & Policy

WHAT IT DOES

What discussion_resolve does on Lockstep

AI agents use discussion_resolve 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_resolve needs a policy

This tool modifies the state of a discussion (marking it resolved) and creates new audit records. While it does not delete data or execute arbitrary code, it irreversibly changes the discussion's status and creates persistent records. The 'creates an auditable record' phrase confirms data creation/modification.

From the tool's definition Tool description states it 'Resolve[s] a discussion with a final decision. Creates an auditable record of the decision.' The act of resolving a discussion and creating a record constitutes modification of data (the discussion state and associated audit logs).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

discussion_resolve Rate-limited

discussion_resolve 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_resolve": {
      "limits": [
        {
          "counter": "discussion_resolve_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_resolve

What does the discussion_resolve tool do? +

Resolve a discussion with a final decision. Creates an auditable record of the decision. 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_resolve? +

Register the Lockstep MCP server in PolicyLayer and add a rule for discussion_resolve: 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_resolve? +

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

Can I rate-limit discussion_resolve? +

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

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

discussion_resolve 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.