hidden_but_available

Hidden tool on current platform

SERVERFrontmcp SOURCEagentfront/frontmcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/hidden-but-available.md

WHAT IT DOES

What hidden_but_available does on Frontmcp

AI agents call hidden_but_available as a supporting operation in Frontmcp workflows.

RISK

Why hidden_but_available is rated Low

The description provides no actionable information about what this tool does, its inputs, or its effects. It only states it is 'hidden' and 'available'. Without knowing what operation it performs, it cannot be reliably categorized beyond 'Other'. Confidence is low due to the uninformative description.

From the tool's definition 'Hidden tool on current platform' - the description is uninformative and does not describe what the tool does

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hidden_but_available 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 hidden_but_available, this is the rule to start with:

hidden_but_available Rate-limited

hidden_but_available gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hidden_but_available": {
      "limits": [
        {
          "counter": "hidden_but_available_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every hidden_but_available call is checked against it from then on.

FAQ

Questions about hidden_but_available

What does the hidden_but_available tool do? +

Hidden tool on current platform. It is categorised as a Other tool in the Frontmcp MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on hidden_but_available? +

Register the Front MCP server in PolicyLayer and add a rule for hidden_but_available: 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.

What risk level is hidden_but_available? +

hidden_but_available is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hidden_but_available? +

Yes. Add a rate_limit block to the hidden_but_available 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.

How do I block hidden_but_available completely? +

Set action: deny in the PolicyLayer policy for hidden_but_available. 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.

What MCP server provides hidden_but_available? +

hidden_but_available 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.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →