get_authors

Retrieve a list of authors from the PulseMCP CMS who can create newsletter posts. Returns formatted markdown with author details. The response is formatted as markdown with: - Total count and pagination info - Author entries, each showing: - Name (as section header) - Slug (required for creating/...

Server Langfuse Observability langfuse-observability-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_authors does on Langfuse Observability

AI agents call get_authors to retrieve information from Langfuse Observability without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_authors needs a policy

This tool performs a simple data retrieval operation with no side effects. It queries a CMS for author information and returns formatted results. There is no capability to modify, delete, or execute any operations. The severity is low because even if an AI agent retrieves this data unnecessarily, it poses minimal risk—author metadata is typically non-sensitive information.

From the tool's definition The tool description explicitly states it will 'Retrieve a list of authors' and 'Returns formatted markdown with author details'.

Questions about get_authors

What does the get_authors tool do? +

Retrieve a list of authors from the PulseMCP CMS who can create newsletter posts. Returns formatted markdown with author details. The response is formatted as markdown with: - Total count and pagination info - Author entries, each showing: - Name (as section header) - Slug (required for creating/updating posts) - Bio (if available) - Avatar image URL (if available) - Created date Use cases: - Find available authors before creating a new newsletter post - Search for a specific author by name to get their slug - List all authors to see who can contribute to the newsletter - Verify an author exists before assigning them to a post - Browse author profiles and specializations - Get author metadata like bio and avatar for display. It is categorised as a Read tool in the Langfuse Observability MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_authors? +

Register the Langfuse Observability MCP server in PolicyLayer and add a rule for get_authors: 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 Langfuse Observability. Nothing to install.

What risk level is get_authors? +

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

Can I rate-limit get_authors? +

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

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

get_authors is provided by the Langfuse Observability MCP server (langfuse-observability-mcp-server). 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.