AI agents call auth-status to retrieve information from My MCP 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 operation, which is a read-only query. It retrieves information about authentication state without creating, modifying, or deleting data. The incomplete description ('Check if you') is somewhat uninformative, but the name and context of a TO DO/task management server suggest this is a simple authentication status retrieval with no side effects.
From the tool's definition Tool name 'auth-status' and description 'Check if you' indicate a query operation that retrieves authentication status information without modifying data.
Documented attack patterns abuse exactly the kind of access auth-status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and My MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for auth-status:
{
"version": "1",
"default": "deny",
"tools": {
"auth-status": {}
}
} auth-status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if you. It is categorised as a Read tool in the My MCP MCP Server, which means it retrieves data without modifying state.
Register the My MCP server in PolicyLayer and add a rule for auth-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 My MCP. Nothing to install.
auth-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 auth-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 auth-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.
auth-status is provided by the My MCP server (jordanburke/microsoft-todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from My MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 My MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.