dev_get_ci_status

Zwróć status deployu/CI z pliku ci-status.json.

Server RPG Ledger MCP Server sepa79/rpg-ledger-mcp
Category Read
Risk class Low
Parameters 00 required

What dev_get_ci_status does on RPG Ledger MCP Server

AI agents call dev_get_ci_status to retrieve information from RPG Ledger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why dev_get_ci_status needs a policy

This tool only queries and returns CI/deployment status from a JSON file. It performs a read-only operation with no side effects, no code execution, no data modification, and no destructive capability. The 'dev_' prefix and status-checking nature confirm it is purely informational. Severity is low because reading CI status poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'dev_get_ci_status' and description 'Zwróć status deployu/CI z pliku ci-status.json' (Return deploy/CI status from ci-status.json file) indicates the tool retrieves status information from a file without modifying or executing operations.

Questions about dev_get_ci_status

What does the dev_get_ci_status tool do? +

Zwróć status deployu/CI z pliku ci-status.json. It is categorised as a Read tool in the RPG Ledger MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dev_get_ci_status? +

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

What risk level is dev_get_ci_status? +

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

Can I rate-limit dev_get_ci_status? +

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

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

dev_get_ci_status is provided by the RPG Ledger MCP Server MCP server (sepa79/rpg-ledger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.