Low Risk

suggest_investigations

Get suggested investigation questions based on codebase topology — weak resolution edges, bridge nodes, hub nodes with uncertain relationships, isolated code, and low-cohesion modules.

How to control suggest_investigations ↓

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

Low Risk

This tool analyzes codebase structure and relationships to surface investigation suggestions, which is fundamentally a query/retrieval operation. It identifies weak points and topological patterns but does not create, modify, delete, execute, or move resources. The blast radius of misuse is minimal—the worst outcome is irrelevant or unhelpful suggestions, not data loss, execution, or side effects.

From the tool's definition Tool description indicates it 'Get[s] suggested investigation questions based on codebase topology' — a retrieval and analysis operation that provides insights without modifying or executing code.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "suggest_investigations": {}
  }
}

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

  1. Create a free account and register Reporecall — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the suggest_investigations tool do? +

Get suggested investigation questions based on codebase topology — weak resolution edges, bridge nodes, hub nodes with uncertain relationships, isolated code, and low-cohesion modules. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on suggest_investigations? +

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

What risk level is suggest_investigations? +

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

Can I rate-limit suggest_investigations? +

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

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

suggest_investigations is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.