license_status

Report the current licensing state: usage tier, whether writes are allowed, and (for a commercial trial) time remaining. Call this if a write was blocked, or during onboarding.

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/license-status.md

WHAT IT DOES

What license_status does on FeatureBoard

AI agents call license_status to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why license_status is rated Low

This tool queries and returns licensing metadata without creating, modifying, deleting, or executing any operations. It is purely informational—a status check. The severest imaginable misuse would be an agent reading this information to decide whether to proceed with other actions, but the tool itself has no blast radius. Classification as Read with low severity is appropriate.

From the tool's definition Tool name 'license_status' and description 'Report the current licensing state' indicate data retrieval only. Verbs used are 'Report' (passive observation) with no mention of modification, deletion, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs license_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For license_status, this is the rule to start with:

license_status Allowed

license_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "license_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about license_status

What does the license_status tool do? +

Report the current licensing state: usage tier, whether writes are allowed, and (for a commercial trial) time remaining. Call this if a write was blocked, or during onboarding. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on license_status? +

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

What risk level is license_status? +

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

Can I rate-limit license_status? +

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

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

license_status is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →