MCP TOOL (NOT a Ludus CLI command) - Prompt user to securely enter a credential via popup dialog and store in OS keyring. IMPORTANT: This is a Ludus MCP server tool, NOT a native Ludus CLI command. Do NOT use
AI agents use get_credential_from_user to create or update resources in LudusMCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LudusMCP Server environment.
This tool writes/stores a credential into the OS keyring. It creates or modifies stored secret data, which is a Write operation. While credential storage could have security implications (e.g., storing a malicious credential), it is reversible and does not execute code or delete data. The severity is medium because misuse could result in credential theft or unauthorized storage of secrets in the OS keyring.
From the tool's definition 'Prompt user to securely enter a credential via popup dialog and store in OS keyring'
Documented attack patterns abuse exactly the kind of access get_credential_from_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LudusMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_credential_from_user:
{
"version": "1",
"default": "deny",
"tools": {
"get_credential_from_user": {
"limits": [
{
"counter": "get_credential_from_user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}get_credential_from_user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
MCP TOOL (NOT a Ludus CLI command) - Prompt user to securely enter a credential via popup dialog and store in OS keyring. IMPORTANT: This is a Ludus MCP server tool, NOT a native Ludus CLI command. Do NOT use. It is categorised as a Write tool in the LudusMCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LudusMCP Server MCP server in PolicyLayer and add a rule for get_credential_from_user: 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 LudusMCP Server. Nothing to install.
get_credential_from_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the get_credential_from_user 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 get_credential_from_user. 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.
get_credential_from_user is provided by the LudusMCP Server MCP server (noctedefensor/ludusmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 LudusMCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 LudusMCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.