New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_instance_info

Get instance metadata: configuration (default) or license info.

SERVERKestra Python MCP Server SOURCEkestra-io/mcp-server-python
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/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.

Questions about get_instance_info

What does the get_instance_info tool do? +

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.

How do I enforce a policy on get_instance_info? +

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.

What risk level is get_instance_info? +

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

Can I rate-limit get_instance_info? +

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.

How do I block get_instance_info completely? +

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.

What MCP server provides get_instance_info? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kestra Python MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.