ops_data_diagnose

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

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/dutydeck/ops-data-diagnose.md

WHAT IT DOES

What ops_data_diagnose does on DutyDeck

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

RISK

Why ops_data_diagnose is rated Low

Even though ops_data_diagnose only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ops_data_diagnose safely

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

ops_data_diagnose Allowed

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

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

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

FAQ

Questions about ops_data_diagnose

What does the ops_data_diagnose tool do? +

Read bounded sanitized diagnostics. MySQL requires database scope with an explicit database and sessions/statements section. PostgreSQL only supports the sessions section with database scope and an explicit database. SQLite uses database main with overview. Redis requires saved configuration and instance scope. SQL text is never returned. Database diagnoses are unavailable if disabled tables could leak through aggregates.${UNTRUSTED_EVIDENCE}. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ops_data_diagnose? +

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

What risk level is ops_data_diagnose? +

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

Can I rate-limit ops_data_diagnose? +

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

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

ops_data_diagnose is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DutyDeck, and thousands of servers like it.

This server

All 247 DutyDeck tools →

Across the catalogue

get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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