get_contests_for_migration
AI agents call get_contests_for_migration to retrieve information from DataFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming pattern and sibling tools suggest this retrieves contest records for migration planning purposes. No side effects or data modification are implied. Confidence is moderate (0.7) because the description is empty, preventing confirmation of exact semantics, but the Read category is most consistent with the tool's naming and operational context.
From the tool's definition Tool name 'get_contests_for_migration' indicates data retrieval with no modification; it is grouped among Read tools like 'get_document', 'get_contests_missing_images', and 'get_contests_with_broken_images' on a CRUD-focused server.
Attacks that exploit this kind of access
get_contests_for_migration. It is categorised as a Read tool in the DataFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataFlow MCP Server MCP server in PolicyLayer and add a rule for get_contests_for_migration: 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 DataFlow MCP Server. Nothing to install.
get_contests_for_migration 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_contests_for_migration 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_contests_for_migration. 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_contests_for_migration is provided by the DataFlow MCP Server MCP server (sreetarak2/dataflow_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_contests_for_migration is one line of DataFlow MCP Server'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 →