Get challenge details (description, files, meta) by ID.
AI agents call challenge_details to retrieve information from CTFd MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about a CTF challenge (description, files, metadata) without modifying, deleting, or executing anything. It is a straightforward read operation that queries and returns data. Severity is low because misuse would only expose information already intended to be accessible within a CTF platform, with no irreversible consequences or external effects.
From the tool's definition Tool name 'challenge_details' and description 'Get challenge details (description, files, meta) by ID' indicate a retrieval-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access challenge_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CTFd MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for challenge_details:
{
"version": "1",
"default": "deny",
"tools": {
"challenge_details": {}
}
}challenge_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get challenge details (description, files, meta) by ID. It is categorised as a Read tool in the CTFd MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CTFd MCP Server MCP server in PolicyLayer and add a rule for challenge_details: 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 CTFd MCP Server. Nothing to install.
challenge_details 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 challenge_details 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 challenge_details. 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.
challenge_details is provided by the CTFd MCP Server MCP server (umbra2728/ctfd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CTFd MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 CTFd MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.