Return personalized user statistics and a usage summary for the current user, showing the value they have received from CorpusIQ: total tool calls, skill invocations, single-source vs multi-source questions answered, plus their top connectors, top tools, and top skills. Use when the user asks for...
Part of the CorpusIQ server.
Free to start. No card required.
AI agents call get_my_usage_stats to retrieve information from CorpusIQ without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_my_usage_stats only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_my_usage_stats": {}
}
}See the full CorpusIQ policy for all 60 tools.
These attack patterns abuse exactly the kind of access get_my_usage_stats gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Return personalized user statistics and a usage summary for the current user, showing the value they have received from CorpusIQ: total tool calls, skill invocations, single-source vs multi-source questions answered, plus their top connectors, top tools, and top skills. Use when the user asks for user stats, usage statistics, 'what have I used?', 'show me my activity', 'how much have I used CorpusIQ?', or wants a recap of their CorpusIQ activity.. It is categorised as a Read tool in the CorpusIQ MCP Server, which means it retrieves data without modifying state.
Register the CorpusIQ MCP server in PolicyLayer and add a rule for get_my_usage_stats: 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 CorpusIQ. Nothing to install.
get_my_usage_stats 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 get_my_usage_stats 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 get_my_usage_stats. 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.
get_my_usage_stats is provided by the CorpusIQ MCP server (https://mcp2.corpusiq.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 60 CorpusIQ tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.