uxi_status

Report whether the optional UXI backend has OAuth credentials configured.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

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/secure-ssid-centralmcp/uxi-status.md

WHAT IT DOES

What uxi_status does on API-Central

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

RISK

Why uxi_status is rated Low

This tool performs a read-only check on configuration status. It retrieves information about whether OAuth credentials are configured but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an attacker could only learn about the credential configuration state, not alter it or trigger actions.

From the tool's definition Tool name 'uxi_status' and description 'Report whether the optional UXI backend has OAuth credentials configured' indicate a query/reporting function that retrieves status information without modifying any state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs uxi_status safely

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

uxi_status Allowed

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

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

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

FAQ

Questions about uxi_status

What does the uxi_status tool do? +

Report whether the optional UXI backend has OAuth credentials configured. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on uxi_status? +

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

What risk level is uxi_status? +

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

Can I rate-limit uxi_status? +

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

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

uxi_status is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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