[FacturaHub] List overdue invoices needing reminders
AI agents call send_reminder to retrieve information from FacturaHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The description explicitly states this tool lists overdue invoices, which is a read/query operation with no side effects. The tool name 'send_reminder' is misleading and suggests it might send communications, but the description contradicts this. Confidence is moderate because the name-description mismatch raises uncertainty about actual behavior — if it does send reminders, it would be Execute/Write category.
From the tool's definition Description says 'List overdue invoices needing reminders' — purely a listing/retrieval operation despite the tool name 'send_reminder' implying an action.
Attacks that exploit this kind of access
[FacturaHub] List overdue invoices needing reminders. It is categorised as a Read tool in the FacturaHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FacturaHub MCP Server MCP server in PolicyLayer and add a rule for send_reminder: 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 FacturaHub MCP Server. Nothing to install.
send_reminder 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 send_reminder 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 send_reminder. 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.
send_reminder is provided by the FacturaHub MCP Server MCP server (santy1422/facturahub-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 →