verify_login_code

SERVERMcp SOURCEhttps://dataecho.ai/mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-dataecho-mcp/verify-login-code.md

WHAT IT DOES

What verify_login_code does on Mcp

AI agents call verify_login_code to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`code`	string	Yes	The one-time code from the email
`email`	string	Yes	Same email as request_login_code

Parameters from the server's own tool schema.

RISK

Why verify_login_code is rated Low

Even though verify_login_code only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_login_code safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For verify_login_code, this is the rule to start with:

verify_login_code Allowed

verify_login_code is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_login_code": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every verify_login_code call is checked against it from then on.

FAQ

Questions about verify_login_code

What does the verify_login_code tool do? +

Complete sign-in with the emailed code. Returns the apiKey ONCE — configure it as the Authorization: Bearer <key> header of this MCP connection (and/or save to ~/.artifact/credentials for the CLI scripts). Never echo it into chat. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does verify_login_code accept? +

verify_login_code accepts 2 parameters: code, email. Required: code, email. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on verify_login_code? +

Register the MCP server in PolicyLayer and add a rule for verify_login_code: 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 Mcp. Nothing to install.

What risk level is verify_login_code? +

verify_login_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_login_code? +

Yes. Add a rate_limit block to the verify_login_code 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.

How do I block verify_login_code completely? +

Set action: deny in the PolicyLayer policy for verify_login_code. 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.

What MCP server provides verify_login_code? +

verify_login_code is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 26 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →