get_org_features

Get feature flags enabled for the organization. Each feature has an ID, name, and enabled status. Useful for checking what capabilities are available on the current plan.

Server Fusebase MCP Server ryan-haver/fusebase-mcp
Category Read
Risk class Low
Parameters 00 required

What get_org_features does on Fusebase MCP Server

AI agents call get_org_features to retrieve information from Fusebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_org_features needs a policy

This tool retrieves organizational feature flag status—a query operation with no side effects. It does not modify, delete, execute code, or create financial obligations. The low severity reflects minimal blast radius: misuse would only expose what features are available on the plan, not enable unauthorized access to those features or cause harm.

From the tool's definition Tool description states it "Get[s] feature flags enabled for the organization" and is described as "Useful for checking what capabilities are available".

Questions about get_org_features

What does the get_org_features tool do? +

Get feature flags enabled for the organization. Each feature has an ID, name, and enabled status. Useful for checking what capabilities are available on the current plan. It is categorised as a Read tool in the Fusebase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_org_features? +

Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for get_org_features: 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 Fusebase MCP Server. Nothing to install.

What risk level is get_org_features? +

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

Can I rate-limit get_org_features? +

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

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

get_org_features is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.