login_audit
Return recent SSH/authentication activity and current logins.
This record as markdown: /tools/mcp-control-plane/login-audit.md
What login_audit does on Mcp Control Plane
AI agents call login_audit to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why login_audit is rated Low
This tool retrieves authentication logs and current login sessions — purely a read/query operation with no side effects. Severity is medium because SSH/auth activity is sensitive security information that could reveal user patterns, active sessions, and potential attack vectors if exposed to a malicious agent.
From the tool's definition Return recent SSH/authentication activity and current logins
Attacks that exploit this kind of access
The rule that runs login_audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For login_audit, this is the rule to start with:
login_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every login_audit call is checked against it from then on.
Questions about login_audit
Return recent SSH/authentication activity and current logins. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for login_audit: 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 Control Plane. Nothing to install.
login_audit 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_audit 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_audit. 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_audit is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
This server
Across the catalogue