dismiss_suggestion · Posterly MCP: Risk & Policy

WHAT IT DOES

What dismiss_suggestion does on Posterly

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

WHY IT NEEDS A POLICY

Why dismiss_suggestion needs a policy

This tool modifies data (suggestion state) reversibly without deleting the underlying data, fitting the Write category. The severity is low because dismissing a suggestion has minimal blast radius — it only affects the visibility of a single suggestion to the user, with no financial, destructive, or external system impacts.

From the tool's definition Tool description explicitly states 'WRITE' and performs 'Dismiss a proactive post suggestion so it stops appearing' — modifying the state of suggestions by marking them as dismissed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dismiss_suggestion Rate-limited

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

FAQ

Questions about dismiss_suggestion

What does the dismiss_suggestion tool do? +

Dismiss a proactive post suggestion so it stops appearing. WRITE: confirm the exact suggestion with the user first. Never dismisses a suggestion that was already turned into a scheduled post (that would break adoption tracking). It is categorised as a Write tool in the Posterly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dismiss_suggestion? +

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

What risk level is dismiss_suggestion? +

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

Can I rate-limit dismiss_suggestion? +

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

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

dismiss_suggestion is provided by the Posterly MCP server (posterly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.