New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_content_details

Full metadata for one Flevy item, by content_id from search_content (e.g. "doc-1234" or "case-567"). Documents return the author with their credentials (headline, bio, LinkedIn, profile URL; pass the author name to search_content's author filter to list more of their documents), full description,...

SERVERFlevy SOURCEhttps://flevy.com/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-flevy-flevy/get-content-details.md

What get_content_details does on Flevy

AI agents call get_content_details to retrieve information from Flevy without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
content_id string Yes The content_id from search_content: "doc-<n>" for documents, "case-<n>" for case studies.

Parameters from the server's own tool schema.

Why get_content_details is rated Low

This tool only retrieves and queries detailed information about existing consulting documents and case studies. It has no ability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only read information about available consulting frameworks and templates without side effects.

From the tool's definition Tool description states it retrieves "Full metadata for one Flevy item" including author credentials, description, summary, page/slide count, price, topics, ranking, and availability of deep dives.

Questions about get_content_details

What does the get_content_details tool do? +

Full metadata for one Flevy item, by content_id from search_content (e.g. "doc-1234" or "case-567"). Documents return the author with their credentials (headline, bio, LinkedIn, profile URL; pass the author name to search_content's author filter to list more of their documents), full description, editor summary, AI summary, and editorial review when available, page/slide count, price, FlevyPro inclusion, management topics, ranking badge, and the number of slide deep dives available. Case studies return the client situation, TL;DR, and summary. Call this before recommending an item so you can describe it accurately and cite the author's credentials, and share the returned flevy.com URL. It is categorised as a Read tool in the Flevy MCP Server, which means it retrieves data without modifying state.

What parameters does get_content_details accept? +

get_content_details accepts 1 parameter: content_id. Required: content_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_content_details? +

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

What risk level is get_content_details? +

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

Can I rate-limit get_content_details? +

Yes. Add a rate_limit block to the get_content_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.

How do I block get_content_details completely? +

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

What MCP server provides get_content_details? +

get_content_details is provided by the Flevy MCP server (https://flevy.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Flevy, and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Flevy's. Pull the full record:

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.