check_rdp

A execute tool on the Mcp Nettools MCP server.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-rdp.md

WHAT IT DOES

What check_rdp does on Mcp Nettools

AI agents invoke check_rdp to trigger actions in Mcp Nettools. 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 check_rdp is rated High

The tool name suggests checking RDP (Remote Desktop Protocol), which on a network diagnostics server likely involves probing or testing an RDP port/service (similar to the sibling 'port check' capability). This falls under Execute as it likely triggers an external network operation. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'check_rdp' on a network diagnostics server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_rdp safely

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

check_rdp Rate-limited

check_rdp 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": {
    "check_rdp": {
      "limits": [
        {
          "counter": "check_rdp_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 Nettools, apply this rule, and every check_rdp call is checked against it from then on.

FAQ

Questions about check_rdp

What does the check_rdp tool do? +

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

How do I enforce a policy on check_rdp? +

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

What risk level is check_rdp? +

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

Can I rate-limit check_rdp? +

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

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

check_rdp is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 235 Mcp Nettools tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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