Low Risk

get_identity

Get identity and connection information for the current Prefect instance.

How to control get_identity ↓

AI agents call get_identity to retrieve information from Prefect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves information about identity and connection details with no side effects. It is a read-only operation that queries existing state without modifying, deleting, or executing code. The low severity reflects minimal blast radius—identity information is typically non-sensitive metadata about the instance configuration.

From the tool's definition Tool name 'get_identity' and description 'Get identity and connection information for the current Prefect instance' indicate pure retrieval of metadata about the Prefect instance and current connection state.

Documented attack patterns abuse exactly the kind of access get_identity gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Prefect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_identity:

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

get_identity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Prefect — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_identity tool do? +

Get identity and connection information for the current Prefect instance. It is categorised as a Read tool in the Prefect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_identity? +

Register the Prefect MCP server in PolicyLayer and add a rule for get_identity: 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 Prefect. Nothing to install.

What risk level is get_identity? +

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

Can I rate-limit get_identity? +

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

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

get_identity is provided by the Prefect MCP server (prefecthq/prefect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prefect tool call.

Deterministic rules across all 14 Prefect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

14 Prefect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.