get_mcp_status

Check if MCP handler and Claude Desktop processes are running

SERVERMCP Autostarter SOURCE199-mcp/mcp-autostarter

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/199-mcp-mcp-autostarter/get-mcp-status.md

WHAT IT DOES

What get_mcp_status does on MCP Autostarter

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

RISK

Why get_mcp_status is rated Low

This tool retrieves status information about running processes. It performs no modifications, deletions, code execution, or financial operations. It is a simple read/query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name is 'get_mcp_status' and description states it 'Check if MCP handler and Claude Desktop processes are running' — a pure query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_mcp_status safely

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

get_mcp_status Allowed

get_mcp_status 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": {
    "get_mcp_status": {}
  }
}

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

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

FAQ

Questions about get_mcp_status

What does the get_mcp_status tool do? +

Check if MCP handler and Claude Desktop processes are running. It is categorised as a Read tool in the MCP Autostarter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_mcp_status? +

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

What risk level is get_mcp_status? +

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

Can I rate-limit get_mcp_status? +

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

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

get_mcp_status is provided by the MCP Autostarter MCP server (199-mcp/mcp-autostarter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Autostarter, and thousands of servers like it.

This server

All 3 MCP Autostarter tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →editor_status on 010 Editor →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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