Low Risk

get_status

Get the current status of the ElizaOS connection

How to control get_status ↓

What get_status does on Society ElizaOS Connector MCP

AI agents call get_status to retrieve information from Society ElizaOS Connector MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_status needs a policy

This tool performs a read-only operation to retrieve status information about an existing connection. It has no side effects, does not modify data, execute code, delete anything, or commit financial obligations. The minimal blast radius if misused would be exposure of connection status details.

From the tool's definition Tool name is 'get_status' and description states 'Get the current status of the ElizaOS connection' — a query operation that retrieves connection status information without modifying any state.

Documented attack patterns abuse exactly the kind of access get_status gives an agent:

How to control get_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Society ElizaOS Connector MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_status": {}
  }
}

get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Society ElizaOS Connector MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_status

What does the get_status tool do? +

Get the current status of the ElizaOS connection. It is categorised as a Read tool in the Society ElizaOS Connector MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_status? +

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

What risk level is get_status? +

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

Can I rate-limit get_status? +

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

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

get_status is provided by the Society ElizaOS Connector MCP server (wearesociety/elizaos_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Society ElizaOS Connector MCP tool call.

Start from Society ElizaOS Connector MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

4 Society ElizaOS Connector MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.