session_send

A execute tool on the Mcp Anything MCP server.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-anything/session-send.md

WHAT IT DOES

What session_send does on Mcp Anything

AI agents invoke session_send to trigger actions in Mcp Anything. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why session_send is rated High

The name 'session_send' implies sending commands or data to an active session, which typically constitutes an Execute-level action. Given the server context (MCP-native bridge to CLI tools), this likely sends commands to a running session. However, the empty description significantly reduces confidence. Severity is rated high because sending arbitrary commands to sessions could have broad impact.

From the tool's definition Tool name 'session_send' suggests sending data/commands to a session; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_send safely

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

session_send Rate-limited

session_send stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session_send": {
      "limits": [
        {
          "counter": "session_send_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about session_send

What does the session_send tool do? +

session_send is a execute tool on the Mcp Anything MCP server. It is categorised as a Execute tool in the Mcp Anything MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on session_send? +

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

What risk level is session_send? +

session_send is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit session_send? +

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

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

session_send is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →