twitter_get_dm_events

Get recent direct message events

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/twitter-get-dm-events.md

WHAT IT DOES

What twitter_get_dm_events does on ScopeGate

AI agents call twitter_get_dm_events to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why twitter_get_dm_events is rated Low

This tool retrieves direct message data from Twitter/X, which is a read-only operation. However, severity is rated 'high' rather than 'low' because direct messages are sensitive personal communications; unauthorized access via an MCP agent could expose private conversations, authentication codes, or confidential information.

From the tool's definition Tool name 'twitter_get_dm_events' and description 'Get recent direct message events' indicate retrieval of existing data with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs twitter_get_dm_events 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_get_dm_events, this is the rule to start with:

twitter_get_dm_events Allowed

twitter_get_dm_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "twitter_get_dm_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about twitter_get_dm_events

What does the twitter_get_dm_events tool do? +

Get recent direct message events. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on twitter_get_dm_events? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for twitter_get_dm_events: 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_get_dm_events? +

twitter_get_dm_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit twitter_get_dm_events? +

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

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

twitter_get_dm_events 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →