Check if the DoorDash session is active
AI agents call login_check to retrieve information from DoorDash MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/checks the current authentication session state without modifying any data or triggering side effects. It is a passive status check, making it a low-severity Read operation.
From the tool's definition Check if the DoorDash session is active
Attacks that exploit this kind of access
Check if the DoorDash session is active. It is categorised as a Read tool in the DoorDash MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DoorDash MCP Server MCP server in PolicyLayer and add a rule for login_check: 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 DoorDash MCP Server. Nothing to install.
login_check 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 login_check 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 login_check. 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.
login_check is provided by the DoorDash MCP Server MCP server (spunkysarb/doordash-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 →