search_report_profile
AI agents call search_report_profile to retrieve information from Insights Knowledge Base MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though search_report_profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
search_report_profile. It is categorised as a Read tool in the Insights Knowledge Base MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Insights Knowledge Base MCP Server MCP server in PolicyLayer and add a rule for search_report_profile: 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 Insights Knowledge Base MCP Server. Nothing to install.
search_report_profile 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 search_report_profile 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 search_report_profile. 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.
search_report_profile is provided by the Insights Knowledge Base MCP Server MCP server (v587d/insightslibrary). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.