glp_write_status

Report whether guarded GLP v2beta1 write tools are enabled.

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/glp-write-status.md

WHAT IT DOES

What glp_write_status does on API-Central

AI agents call glp_write_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 glp_write_status is rated Low

This tool only reports/queries the status of whether write tools are enabled — it does not perform any writes itself. It is a read/status-check operation with no side effects.

From the tool's definition Report whether guarded GLP v2beta1 write tools are enabled

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs glp_write_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 glp_write_status, this is the rule to start with:

glp_write_status Allowed

glp_write_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": {
    "glp_write_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 glp_write_status call is checked against it from then on.

FAQ

Questions about glp_write_status

What does the glp_write_status tool do? +

Report whether guarded GLP v2beta1 write tools are enabled. 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 glp_write_status? +

Register the API-Central MCP server in PolicyLayer and add a rule for glp_write_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 glp_write_status? +

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

Can I rate-limit glp_write_status? +

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

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

glp_write_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 →