secret
Set/get/list/delete a session secret via this.secureStore
This record as markdown: /tools/frontmcp/secret.md
What secret does on Frontmcp
AI agents call secret to permanently remove resources in Frontmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why secret is rated Critical
The tool supports deletion of session secrets ('delete a session secret'), which is an irreversible destructive operation. Since the most severe applicable category must be chosen, and deletion of secrets could permanently remove authentication credentials, Destructive is appropriate.
From the tool's definition Set/get/list/delete a session secret via this.secureStore
Attacks that exploit this kind of access
The rule that runs 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 secret, this is the rule to start with:
secret is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every secret call is checked against it from then on.
Questions about secret
Set/get/list/delete a session secret via this.secureStore. It is categorised as a Destructive tool in the Frontmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Front MCP server in PolicyLayer and add a rule for 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.
secret is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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 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.
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.
Across the catalogue