Check if a specific person has submitted their weekly report
AI agents call check_person_report 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 queries submission status for a person, returning a boolean or status indicator about whether a report exists. It performs no side effects, creates no data, executes no commands, and cannot delete or modify anything. This is purely a read operation against the reporting database/sheet. Low severity because misuse would only expose individual submission status information, not cause operational harm.
From the tool's definition Tool description states "Check if a specific person has submitted their weekly report" - a query operation that retrieves or verifies submission status.
Attacks that exploit this kind of access
Check if a specific person has submitted their weekly report. 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 check_person_report: 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.
check_person_report 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 check_person_report 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 check_person_report. 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.
check_person_report 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 →