diagnostic_tool

THE RISK

High Risk

Why diagnostic_tool needs a policy

The tool actively runs operations (diagnostic checks) against the application, which constitutes execution of processes. It is not purely a passive read — diagnostics may invoke system calls, probe endpoints, or trigger internal routines.

From the tool's definition 'Runs diagnostic checks on the application' — actively executes checks against the application

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

POLICY

How to control diagnostic_tool

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "diagnostic_tool": {
      "limits": [
        {
          "counter": "diagnostic_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

diagnostic_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Tally MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Tally MCP tools

Destructive bulk_delete_forms 🚫 DEPRECATED: Use confirm_bulk_delete instead. This tool now requires human confirmation Destructive confirm_bulk_delete HUMAN CONFIRMATION: Confirm bulk deletion after reviewing preview. Requires explicit user Destructive delete_form Delete a Tally form permanently Write create_form Create a new Tally form with specified fields and configuration. This tool converts simple Write generate_template Generate a form template based on requirements or use case Write manage_team Manage team members and permissions Write manage_workspace Manage workspace settings and information Write modify_form Modify an existing Tally form

All 18 Tally MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Tally MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about diagnostic_tool

What does the diagnostic_tool tool do? +

Runs diagnostic checks on the application. It is categorised as a Execute tool in the Tally MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on diagnostic_tool? +

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

What risk level is diagnostic_tool? +

diagnostic_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit diagnostic_tool? +

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

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

diagnostic_tool is provided by the Tally MCP server (learnwithcc/tally-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tally MCP tool call.

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

CHECK YOUR STACK →