Check if authentication token is valid.
AI agents call check_auth to retrieve information from RTM 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 status check on an authentication token—a read-only verification operation with no side effects. It retrieves or queries the validity state of an existing token without creating, modifying, deleting, or executing any changes to tasks, lists, notes, or any other data. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'check_auth' and description 'Check if authentication token is valid' indicate a query operation that verifies credentials without modifying any data or triggering external operations.
Attacks that exploit this kind of access
Check if authentication token is valid. It is categorised as a Read tool in the RTM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RTM MCP Server MCP server in PolicyLayer and add a rule for check_auth: 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 RTM MCP Server. Nothing to install.
check_auth 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_auth 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_auth. 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_auth is provided by the RTM MCP Server MCP server (ljadach/rtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
check_auth is one line of RTM MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →