AI agents call api_login as a supporting operation in CyberMCP workflows.
With no description, the exact behavior is unknown. Based on the name 'api_login' and sibling tools like 'basic_auth' and 'oauth2_auth', this tool likely performs an authentication operation (sending credentials to an API). This could be a Write or Execute action, but it may also simply be a read-like authentication check.
From the tool's definition Tool name is 'api_login' and the description is empty or uninformative. Server context mentions authentication-related tools (basic_auth, oauth2_auth, clear_auth, auth_bypass_check).
Documented attack patterns abuse exactly the kind of access api_login gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CyberMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for api_login:
{
"version": "1",
"default": "deny",
"tools": {
"api_login": {
"limits": [
{
"counter": "api_login_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}api_login gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
api_login. It is categorised as a Other tool in the CyberMCP MCP Server, which means it performs auxiliary operations.
Register the Cyber MCP server in PolicyLayer and add a rule for api_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 CyberMCP. Nothing to install.
api_login is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the api_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 api_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.
api_login is provided by the Cyber MCP server (ricauts/cybermcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CyberMCP, 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.
14 CyberMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.