get_instance_info
Get instance metadata: configuration (default) or license info.
This record as markdown: /tools/kestra-io-mcp-server-python/get-instance-info.md
What get_instance_info does on Kestra Python MCP Server
AI agents call get_instance_info to retrieve information from Kestra Python MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_instance_info is rated Low
This is a straightforward read-only operation that queries instance information without side effects. While instance configuration details may be sensitive for threat modeling purposes, the tool itself performs no destructive, modifying, or executable operations. Severity is low because metadata retrieval is a passive information-gathering action with limited blast radius for unintended AI misuse.
From the tool's definition Tool retrieves instance metadata including configuration and license info. The verb 'get' and description 'Get instance metadata' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_instance_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kestra Python MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_instance_info, this is the rule to start with:
get_instance_info 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 Kestra Python MCP Server, apply this rule, and every get_instance_info call is checked against it from then on.
Questions about get_instance_info
Get instance metadata: configuration (default) or license info. It is categorised as a Read tool in the Kestra Python MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for get_instance_info: 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 Kestra Python MCP Server. Nothing to install.
get_instance_info 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_instance_info 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_instance_info. 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_instance_info is provided by the Kestra Python MCP Server MCP server (kestra-io/mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kestra Python MCP Server, and thousands of servers like it.
This server
Across the catalogue