resolve_discussion

THE RISK

Medium Risk

Why resolve_discussion needs a policy

The tool modifies discussion metadata (resolution status) in a CMS system. This is Write-category because it changes data state reversibly without deleting content or executing arbitrary code. Severity is medium because unwarranted resolution of discussions could disrupt collaboration workflows and hide important feedback, but the impact is limited to one resource type and remains recoverable.

From the tool's definition Tool performs 'Marks a discussion as resolved' - a state change operation that modifies discussion data in Storyblok. This is a reversible write operation that updates an existing resource's status field.

Documented attack patterns abuse exactly the kind of access resolve_discussion gives an agent:

POLICY

How to control resolve_discussion

PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_discussion:

policy.json

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

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

Create a free account and register Storyblok MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Storyblok MCP Server tools

Destructive bulk_delete_stories Deletes multiple stories in Storyblok. Destructive delete_access_token Delete an access token from the current Storyblok space using the Management API. Destructive delete_approval Deletes an approval from a specified Storyblok space. Destructive delete_asset Deletes an asset from Storyblok. Destructive delete_asset_folder Delete an asset folder from the current Storyblok space. Destructive delete_branch Deletes a branch (pipeline) by its ID in a Storyblok space. Destructive delete_collaborator Deletes a collaborator from a specified Storyblok space. Destructive delete_comment Deletes a comment from a discussion via the Storyblok Management API.

All 159 Storyblok MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about resolve_discussion

What does the resolve_discussion tool do? +

Marks a discussion as resolved via the Storyblok Management API. It is categorised as a Write tool in the Storyblok 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 resolve_discussion? +

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

What risk level is resolve_discussion? +

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

Can I rate-limit resolve_discussion? +

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

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

resolve_discussion is provided by the Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Storyblok MCP Server tool call.

Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →