Find product areas and business capability pages relevant to a query. Returns business-facing context plus supporting files and symbols.
AI agents call business_context_query 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.
This tool retrieves and queries business context information from a codebase index without creating, modifying, deleting, or executing any operations. It is a pure read operation that injects relevant code context to support AI reasoning. The 'business_context_query' name and description confirm data retrieval only, making it a Read category tool with low risk.
From the tool's definition Tool description states it 'Find[s] product areas and business capability pages relevant to a query' and 'Returns business-facing context plus supporting files and symbols.' The verb 'Find' and 'Returns' indicate retrieval/querying operations with no…
Documented attack patterns abuse exactly the kind of access business_context_query 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 business_context_query:
{
"version": "1",
"default": "deny",
"tools": {
"business_context_query": {}
}
}business_context_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find product areas and business capability pages relevant to a query. Returns business-facing context plus supporting files and symbols. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.
Register the Reporecall MCP server in PolicyLayer and add a rule for business_context_query: 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.
business_context_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the business_context_query 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.
Set action: deny in the PolicyLayer policy for business_context_query. 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.
business_context_query 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.
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.