Check if the Unosend API is accessible and the API key is valid.
AI agents call check_api_status to retrieve information from Unosend MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to verify API availability and credential validity. It has no side effects, does not create, modify, or delete data, and does not trigger external operations. It is purely informational, making it a Read category risk with low severity.
From the tool's definition Tool name 'check_api_status' and description 'Check if the Unosend API is accessible and the API key is valid' indicate a status check operation that retrieves API health information without modifying or executing actions.
Attacks that exploit this kind of access
Check if the Unosend API is accessible and the API key is valid. It is categorised as a Read tool in the Unosend MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unosend MCP Server MCP server in PolicyLayer and add a rule for check_api_status: 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 Unosend MCP Server. Nothing to install.
check_api_status 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_api_status 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_api_status. 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_api_status is provided by the Unosend MCP Server MCP server (unosend/mcp-server). 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 →