info

Runs

Server Python Dave-London/Pare
Category Execute
Risk class High
Parameters 00 required

What info does on Python

AI agents invoke info to trigger actions in Python. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Why info needs a policy

The server description indicates it executes structured Python tooling commands. The description 'Runs' (truncated) strongly implies execution of some command or tool. Given the context of sibling tools like ansible-playbook, bazel, and the server's purpose of running Python tools, this likely executes a command.

From the tool's definition Tool name is 'info' on a server that runs Python tools (ruff, mypy, pip, uv, black, pytest). The description only says 'Runs' with no further detail.

Questions about info

What does the info tool do? +

Runs. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on info? +

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

What risk level is info? +

info is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit info? +

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

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

info is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

info is one line of Python's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.