Check whether a set of constraints can be simultaneously satisfied. Uses the twist-compression operator to detect structural obstructions — fundamental conflicts in the constraint system that cannot be resolved by adjusting any single field. Returns obstruction type, magnitude, and the specific c...
Risk signalsHandles credentials or secrets (api_key)
Part of the Governance Platform server.
Free to start. No card required.
AI agents call check_feasibility to retrieve information from Governance Platform without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though check_feasibility only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"check_feasibility": {}
}
}See the full Governance Platform policy for all 31 tools.
These attack patterns abuse exactly the kind of access check_feasibility gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check whether a set of constraints can be simultaneously satisfied. Uses the twist-compression operator to detect structural obstructions — fundamental conflicts in the constraint system that cannot be resolved by adjusting any single field. Returns obstruction type, magnitude, and the specific constraint interactions causing the conflict. Fast pre-check before running full validation. Args: api_key: GeodesicAI API key (starts with gai_) constraints: List of derivation rules and formal constraints to check field_values: Current field values (numeric key-value pairs). It is categorised as a Read tool in the Governance Platform MCP Server, which means it retrieves data without modifying state.
Register the Governance Platform MCP server in PolicyLayer and add a rule for check_feasibility: 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 Governance Platform. Nothing to install.
check_feasibility 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 check_feasibility 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 check_feasibility. 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.
check_feasibility is provided by the Governance Platform MCP server (https://app.geodesiclabs.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Governance Platform tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.