get_connector_status

SERVERGuildControl MCP SOURCEguildctl

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/app-lasers-guildcontrol-discord/get-connector-status.md

WHAT IT DOES

What get_connector_status does on GuildControl MCP

AI agents call get_connector_status to retrieve information from GuildControl MCP 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_connector_status is rated Low

Tool queries bot identity, guild count, and configuration metadata without modifying data.

From the tool's definition Verify configured Discord application, report scope, without reading messages.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_connector_status safely

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

get_connector_status Allowed

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

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

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

FAQ

Questions about get_connector_status

What does the get_connector_status tool do? +

Verify the configured Discord application and bot identity, count the first guild page, and report effective connector scope plus the durable reviewed-write coordination boundary without reading messages. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_connector_status? +

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

What risk level is get_connector_status? +

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

Can I rate-limit get_connector_status? +

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

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

get_connector_status is provided by the GuildControl MCP server (guildctl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GuildControl, and thousands of servers like it.

This server

All 258 GuildControl 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 →