get_global_config
Read FeatureBoard
This record as markdown: /tools/ai-featureboard-featureboard/get-global-config.md
What get_global_config does on FeatureBoard
AI agents call get_global_config 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.
Why get_global_config is rated Low
This tool retrieves configuration data from the FeatureBoard system without creating, modifying, deleting, or executing any operations. Read operations on configuration have low blast radius since they only expose existing data. Confidence is high because the description explicitly labels this as a read operation.
From the tool's definition Tool name is 'get_global_config' and description states 'Read FeatureBoard' — explicitly indicates a read operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_global_config 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 get_global_config, this is the rule to start with:
get_global_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every get_global_config call is checked against it from then on.
Questions about get_global_config
Read FeatureBoard. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for get_global_config: 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.
get_global_config 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 get_global_config 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 get_global_config. 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.
get_global_config 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.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue