Get statistics about weekly report submissions
AI agents call get_submission_stats to retrieve information from Weekly Report Checker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a data retrieval operation to generate analytics and statistics on existing report submission data. It does not create, modify, delete, or execute any operations; it only reads and aggregates information from the Google Sheet. This is a straightforward Read category tool with low risk of misuse by an AI agent.
From the tool's definition Tool retrieves statistics about weekly report submissions with no side effects. The description uses language consistent with querying/viewing data: 'Get statistics about weekly report submissions.' The parent server description also indicates this is for…
Attacks that exploit this kind of access
Get statistics about weekly report submissions. It is categorised as a Read tool in the Weekly Report Checker MCP Server, which means it retrieves data without modifying state.
Register the Weekly Report Checker MCP server in PolicyLayer and add a rule for get_submission_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 Weekly Report Checker. Nothing to install.
get_submission_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_submission_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_submission_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_submission_stats is provided by the Weekly Report Checker MCP server (kaneyxx/weekly-report-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →