bag_health_mcp__list_export_files

bag_health_mcp__list_export_files

Server Pypi:bag Health pypi:bag-health-mcp
Category Read
Risk class Low
Parameters 00 required

What bag_health_mcp__list_export_files does on Pypi:bag Health

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

Why bag_health_mcp__list_export_files needs a policy

The tool appears to list or enumerate export files without modifying, deleting, or executing operations. Within the context of a health surveillance dashboard, listing available exports is a retrieval operation with no side effects. Confidence is slightly reduced due to missing description, but the functional intent is clear from naming and server context.

From the tool's definition Tool name 'list_export_files' indicates retrieval/enumeration of existing files. Description is empty, but the naming pattern and sibling tools (download_export, get_data_version, get_disease_data, list_diseases, list_series) all perform read-only queries…

Questions about bag_health_mcp__list_export_files

What does the bag_health_mcp__list_export_files tool do? +

bag_health_mcp__list_export_files. It is categorised as a Read tool in the Pypi:bag Health MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bag_health_mcp__list_export_files? +

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

What risk level is bag_health_mcp__list_export_files? +

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

Can I rate-limit bag_health_mcp__list_export_files? +

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

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

bag_health_mcp__list_export_files is provided by the Pypi:bag Health MCP server (pypi:bag-health-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.