get_rule_details

ServerDingo MCP Server
CategoryRead

WHAT IT DOES

What get_rule_details does on Dingo MCP Server

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

THE RISK

Low Risk

Why get_rule_details needs a policy

This tool performs a read-only query operation to fetch metadata about a rule. It retrieves and returns information without creating, modifying, deleting, or executing any operations. The action is informational only with no side effects.

From the tool's definition Tool description states it 'Retrieves information' and 'Get detailed information about a specific Dingo rule' with no modification or execution capabilities. The function signature takes only a rule_name parameter and returns rule details.

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

POLICY

How to control get_rule_details

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_rule_details": {}
  }
}

get_rule_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dingo MCP Server tools

Execute run_dingo_evaluation Runs a Dingo evaluation (rule-based or LLM-based) on a file. Infers data_format from Execute run_quick_evaluation Run a simplified Dingo evaluation based on a high-level goal. Automatically infers th Read get_llm_details Get detailed information about a specific Dingo LLM. Retrieves information including Read get_prompt_details Get detailed information about an LLM's embedded prompt. In the new architecture, pro Read list_dingo_components Lists available Dingo rule groups, registered LLM model identifiers, and prompt definition

All 6 Dingo MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_rule_details

What does the get_rule_details tool do? +

Get detailed information about a specific Dingo rule. Retrieves information including the rule's description, parameters, and evaluation characteristics. Args: rule_name: The name of the rule to get details for (e.g., 'RuleContentNull', 'RuleDocRepeat'). Returns: A dictionary containing details about the rule. It is categorised as a Read tool in the Dingo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_rule_details? +

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

What risk level is get_rule_details? +

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

Can I rate-limit get_rule_details? +

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

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

get_rule_details is provided by the Dingo MCP Server MCP server (migoxlab/dingo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dingo MCP Server tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

6 Dingo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.