Create a new comment on traces, observations, sessions, or prompts.
AI agents use create_comment to create or update resources in Langfuse MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Langfuse MCP Server environment.
This tool creates new comments, which are metadata additions that can be modified or deleted later. While it modifies state in the Langfuse system, the operation is reversible and does not destroy data or execute arbitrary code.
From the tool's definition Tool name 'create_comment' and description 'Create a new comment' explicitly indicate creation of new data on traces, observations, sessions, or prompts—a reversible write operation.
Attacks that exploit this kind of access
Create a new comment on traces, observations, sessions, or prompts. It is categorised as a Write tool in the Langfuse MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Langfuse MCP Server MCP server in PolicyLayer and add a rule for create_comment: 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 MCP Server. Nothing to install.
create_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_comment 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 create_comment. 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.
create_comment is provided by the Langfuse MCP Server MCP server (therealsachin/langfuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →