Authenticate with Evaluar using username and password. Returns success status and masked token info.
AI agents invoke auth_login to trigger actions in Evaluar MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Authentication involves executing an external operation against the Evaluar platform (submitting credentials, establishing a session/token). It is not a simple read, nor does it write/modify user data, but it triggers an external session creation. Misuse could expose credentials or create unauthorized sessions, warranting medium severity.
From the tool's definition Authenticate with Evaluar using username and password. Returns success status and masked token info.
Attacks that exploit this kind of access
Authenticate with Evaluar using username and password. Returns success status and masked token info. It is categorised as a Execute tool in the Evaluar MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Evaluar MCP Server MCP server in PolicyLayer and add a rule for auth_login: 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 Evaluar MCP Server. Nothing to install.
auth_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the auth_login 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_login. 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_login is provided by the Evaluar MCP Server MCP server (yarmijosp94/evaluar-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 →