Check which MCP functions are available based on account permissions
AI agents call check_function_availability to retrieve information from Fastmail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a purely informational tool that queries the permission model and available functions. It has no side effects, creates no data changes, executes no operations, and poses minimal risk if misused — an AI agent calling it repeatedly would only retrieve redundant permission information. Classified as Read.
From the tool's definition Tool name is 'check_function_availability' and description states it 'Check[s] which MCP functions are available based on account permissions' — this is a query/inspection operation that retrieves metadata about available capabilities without modifying any…
Documented attack patterns abuse exactly the kind of access check_function_availability gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fastmail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_function_availability:
{
"version": "1",
"default": "deny",
"tools": {
"check_function_availability": {}
}
} check_function_availability is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check which MCP functions are available based on account permissions. It is categorised as a Read tool in the Fastmail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fastmail MCP Server MCP server in PolicyLayer and add a rule for check_function_availability: 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 Fastmail MCP Server. Nothing to install.
check_function_availability 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 check_function_availability 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 check_function_availability. 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.
check_function_availability is provided by the Fastmail MCP Server MCP server (madllama25/fastmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fastmail MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
38 Fastmail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.