// MCP TOOL REFERENCE

reporting_guide

Part of the Senzing MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

senzing/entity-resolution Execute Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke reporting_guide to trigger processes or run actions in Senzing. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON REPORTING_GUIDE

reporting_guide can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

senzing-entity-resolution.yaml

tools:
  reporting_guide:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Senzing policy for all 13 tools.

// DETAILS

Tool Name reporting_guide

Category Execute

MCP Server Senzing MCP Server

Risk Level High

// MORE SENZING TOOLS

Destructive mapping_workflow Destructive sdk_guide Write generate_scaffold Write submit_feedback Read analyze_record Read download_resource Read explain_error_code Read find_examples

View all 13 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like reporting_guide have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

reporting_guide is one of the high-risk operations in Senzing. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the reporting_guide tool do? +

Guided reporting and visualization for Senzing entity resolution results. Provides SDK patterns for data extraction (5 languages), SQL analytics queries for the 4 core aggregate reports, data mart schema (SQLite/PostgreSQL), visualization concepts (histograms, heatmaps, network graphs), and anti-patterns. Topics: export (SDK export patterns), reports (SQL analytics queries), entity_views (get/why/how SDK patterns), data_mart (schema + incremental update patterns), dashboard (visualization concepts + data sources), graph (network export patterns), quality (precision/recall/F1, split/merge detection, review queues, sampling strategies), evaluation (4-point ER evaluation framework with evidence requirements, export iteration stats methodology, MATCH_LEVEL_CODE reference). Returns decision trees when language/scale not specified.. It is categorised as a Execute tool in the Senzing MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reporting_guide? +

Add a rule in your Intercept YAML policy under the tools section for reporting_guide. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Senzing MCP server.

What risk level is reporting_guide? +

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

Can I rate-limit reporting_guide? +

Yes. Add a rate_limit block to the reporting_guide rule in your Intercept 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 reporting_guide completely? +

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

reporting_guide is provided by the Senzing MCP server (senzing/entity-resolution). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

reporting_guide

Enforce policies on Senzing