elicit-secret
Ask the calling client for a secret via elicitation.
This record as markdown: /tools/frontmcp/elicit-secret.md
What elicit-secret does on Frontmcp
AI agents call elicit-secret to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why elicit-secret is rated Low
This tool retrieves sensitive information (a secret) from a client through an elicitation request. While it is fundamentally a Read operation (obtaining data), the severity is high because the tool explicitly handles secrets, which are sensitive authentication or authorization credentials. Misuse by an AI agent could trick users into revealing secrets through social engineering via the elicitation mechanism.
From the tool's definition The tool 'elicit-secret' is described as 'Ask the calling client for a secret via elicitation.' It retrieves or queries information (a secret) from the client rather than modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs elicit-secret safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For elicit-secret, this is the rule to start with:
elicit-secret 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 Frontmcp, apply this rule, and every elicit-secret call is checked against it from then on.
Questions about elicit-secret
Ask the calling client for a secret via elicitation. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for elicit-secret: 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 Frontmcp. Nothing to install.
elicit-secret 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 elicit-secret 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 elicit-secret. 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.
elicit-secret is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue