Low Risk

list_blueprints

List Blueprints owned by the calling account. Returns each Blueprint's name, workflow identifier, mode, and field/rule/constraint counts. Use the workflow_name as the 'blueprint' parameter when calling validate. Blueprint modes — important for agents that summarize results: - "observe" (Observati...

Risk signalsHandles credentials or secrets (api_key)

Part of the Governance Platform server.

list_blueprints is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GOVERNANCE PLATFORM →

Free to start. No card required.

AI agents call list_blueprints 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 list_blueprints 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_blueprints": {}
  }
}

See the full Governance Platform policy for all 31 tools.

Get this rule live on your own Governance Platform server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GOVERNANCE PLATFORM →

View all 31 tools →

These attack patterns abuse exactly the kind of access list_blueprints gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_blueprints only ever does what you allow.

SECURE GOVERNANCE PLATFORM →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_blueprints tool do? +

List Blueprints owned by the calling account. Returns each Blueprint's name, workflow identifier, mode, and field/rule/constraint counts. Use the workflow_name as the 'blueprint' parameter when calling validate. Blueprint modes — important for agents that summarize results: - "observe" (Observation mode): the platform validates data against the Blueprint's rules and returns PASS, FAIL, or REVIEW with repair suggestions. Validation is detection-only; the caller decides what to do with the result. - "enforce" (Execution mode): the platform performs the same validation AND authorizes downstream side effects. Side effects are blocked if validation fails. In this mode, rules that compute derived values (like totals) publish the platform's computed result as authoritative, so downstream consumers see the canonical value rather than the agent's. Both modes run the same rule checks. The difference is what happens after validation, not during it. Scope: only Blueprints created by the calling account are returned. Use validate / repair / etc. with the workflow_name to operate on them. Args: api_key: GeodesicAI API key (starts with gai_). It is categorised as a Read tool in the Governance Platform MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_blueprints? +

Register the Governance Platform MCP server in PolicyLayer and add a rule for list_blueprints: 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.

What risk level is list_blueprints? +

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

Can I rate-limit list_blueprints? +

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

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

list_blueprints 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.

Enforce policy on every Governance Platform tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.