twitter_mute_user

Mute a user

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/twitter-mute-user.md

WHAT IT DOES

What twitter_mute_user does on ScopeGate

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

RISK

Why twitter_mute_user is rated Medium

Muting a user is a reversible write action that modifies the authenticated user's social graph/settings by suppressing another user's content. It can be undone by unmuting. No data is deleted, no money moves, no code is executed. Severity is medium because misuse could silently mute legitimate contacts or communications at scale.

From the tool's definition 'Mute a user' — muting modifies account relationship/settings state

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs twitter_mute_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For twitter_mute_user, this is the rule to start with:

twitter_mute_user Rate-limited

twitter_mute_user 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": {
    "twitter_mute_user": {
      "limits": [
        {
          "counter": "twitter_mute_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every twitter_mute_user call is checked against it from then on.

FAQ

Questions about twitter_mute_user

What does the twitter_mute_user tool do? +

Mute a user. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on twitter_mute_user? +

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

What risk level is twitter_mute_user? +

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

Can I rate-limit twitter_mute_user? +

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

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

twitter_mute_user is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →