connector_status

Is a file connector connected for your account, and is this deployment configured for it? Returns

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

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/io-github-proagentstore-platform/connector-status.md

WHAT IT DOES

What connector_status does on ProAgentStore

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

RISK

Why connector_status is rated Low

Queries connector configuration state with no side effects or data modification.

From the tool's definition connector_status returns deployment configuration and connection status

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs connector_status safely

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

connector_status Allowed

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

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

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

FAQ

Questions about connector_status

What does the connector_status tool do? +

Is a file connector connected for your account, and is this deployment configured for it? Returns. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on connector_status? +

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

What risk level is connector_status? +

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

Can I rate-limit connector_status? +

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

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

connector_status is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

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