get_board_common_preference
Read the CommonBoardPreference row attached to board.app.Board. Returns present=false when the preference row is absent and never creates it.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-board-common-preference.md
What get_board_common_preference does on Huly
AI agents call get_board_common_preference to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_board_common_preference is rated Low
This tool queries and retrieves preference data from a board without modifying, deleting, or executing any operations. It is a pure read operation that returns existing data or indicates absence without creating anything. This fits the Read category with low severity since preference data access poses minimal risk.
From the tool's definition Tool description explicitly states 'Read the CommonBoardPreference row' and 'never creates it.' The action is retrieval-only with no side effects.
Attacks that exploit this kind of access
The rule that runs get_board_common_preference safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_board_common_preference, this is the rule to start with:
get_board_common_preference 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 Huly, apply this rule, and every get_board_common_preference call is checked against it from then on.
Questions about get_board_common_preference
Read the CommonBoardPreference row attached to board.app.Board. Returns present=false when the preference row is absent and never creates it. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_board_common_preference: 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 Huly. Nothing to install.
get_board_common_preference 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_board_common_preference 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_board_common_preference. 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_board_common_preference is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue