imf-get-dataflow
Get metadata for a single IMF dataflow.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/imf-get-dataflow.md
What imf-get-dataflow does on Meta Data Mcp
AI agents call imf-get-dataflow to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why imf-get-dataflow is rated Low
This tool retrieves metadata about an IMF dataflow—a purely informational operation with no side effects, data modification, code execution, or destructive capability. It is consistent with other Read operations in the server (arxiv-get-paper, au-data-gov-get-dataset) and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'imf-get-dataflow' and description 'Get metadata for a single IMF dataflow' indicate a query/retrieval operation. The verb 'Get' and noun 'metadata' confirm read-only access to IMF data without modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs imf-get-dataflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For imf-get-dataflow, this is the rule to start with:
imf-get-dataflow 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 Meta Data Mcp, apply this rule, and every imf-get-dataflow call is checked against it from then on.
Questions about imf-get-dataflow
Get metadata for a single IMF dataflow. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for imf-get-dataflow: 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 Meta Data Mcp. Nothing to install.
imf-get-dataflow 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 imf-get-dataflow 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 imf-get-dataflow. 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.
imf-get-dataflow is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue