Returns a summary of the AppSignal GraphQL API schema, including available Query fields, Mutation fields, and all type definitions with their names, kinds, and descriptions. This is a discovery tool - use it BEFORE constructing a custom_graphql_query to understand what data is available. The summ...
AI agents call get_graphql_schema 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.
This is purely an informational/discovery tool that retrieves and exposes schema metadata about available GraphQL operations. It performs no mutations, deletions, or external operations—it only reads and summarizes existing schema information. This is a classic Read category action: data retrieval with no side effects.
From the tool's definition Tool name and description: 'Returns a summary of the AppSignal GraphQL API schema' and 'This is a discovery tool - use it BEFORE constructing a custom_graphql_query to understand what data is available.' The tool retrieves schema metadata (Query fields,…
Attacks that exploit this kind of access
Returns a summary of the AppSignal GraphQL API schema, including available Query fields, Mutation fields, and all type definitions with their names, kinds, and descriptions. This is a discovery tool - use it BEFORE constructing a custom_graphql_query to understand what data is available. The summary provides: - Query fields: What data you can fetch (app, organization, viewer, timezones) - Mutation fields: What actions you can perform - Types: All available types with their kind (type/input/enum/interface/union/scalar) and field counts After reviewing this summary, use get_graphql_schema_details with specific type names to see full field definitions before writing your query. IMPORTANT: Prefer using the other specialized tools (get_exception_incident, search_logs, get_metrics, etc.) for common operations. Only use custom GraphQL queries when: - The specialized tools don. It is categorised as a Read tool in the Langfuse Observability MCP Server, which means it retrieves data without modifying state.
Register the Langfuse Observability MCP server in PolicyLayer and add a rule for get_graphql_schema: 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.
get_graphql_schema 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_graphql_schema 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_graphql_schema. 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_graphql_schema 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.
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 →