get_check_results

Collect the results of a background static-check run: by runId, else the newest run for a ticket, else the newest run overall. Returns the run

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/get-check-results.md

WHAT IT DOES

What get_check_results does on FeatureBoard

AI agents call get_check_results 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 get_check_results is rated Low

This tool only reads data from completed static-check runs. It does not create, modify, delete, or execute any operations. The 'collect results' and 'returns the run' language indicates pure data retrieval with no side effects. Severity is low because exposing test/check results poses minimal risk—an agent cannot misuse this to cause harm.

From the tool's definition 'Collect the results of a background static-check run' — the tool retrieves and returns check results without modifying, deleting, or executing anything. It is a query/fetch operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_check_results 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_check_results, this is the rule to start with:

get_check_results Allowed

get_check_results 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": {
    "get_check_results": {}
  }
}

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 get_check_results call is checked against it from then on.

FAQ

Questions about get_check_results

What does the get_check_results tool do? +

Collect the results of a background static-check run: by runId, else the newest run for a ticket, else the newest run overall. Returns the run. 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 get_check_results? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for get_check_results: 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 get_check_results? +

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

Can I rate-limit get_check_results? +

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

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

get_check_results 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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