always_available

A tool with no availableWhen constraint — always visible

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/always-available.md

WHAT IT DOES

What always_available does on Frontmcp

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

RISK

Why always_available is rated Low

The description only explains the tool's visibility/availability behavior (no constraint on when it appears), not what it actually does. There is no information about reads, writes, executions, or any side effects. The description is essentially uninformative about functionality, so this falls into 'Other' with low confidence.

From the tool's definition A tool with no availableWhen constraint — always visible

Attacks that exploit this kind of access

RECOMMENDED RULE

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

always_available Rate-limited

always_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": {
    "always_available": {
      "limits": [
        {
          "counter": "always_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 always_available call is checked against it from then on.

FAQ

Questions about always_available

What does the always_available tool do? +

A tool with no availableWhen constraint — always visible. 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 always_available? +

Register the Front MCP server in PolicyLayer and add a rule for always_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 always_available? +

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

Can I rate-limit always_available? +

Yes. Add a rate_limit block to the always_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 always_available completely? +

Set action: deny in the PolicyLayer policy for always_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 always_available? +

always_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 →