Returns full GraphQL type definitions for the specified type names. Use this after get_graphql_schema to get detailed field information for types you need in your custom query. This tool provides the complete schema definition including: - All fields with their types and arguments - Field descrip...
AI agents call get_graphql_schema_details to retrieve information from Pointsyeah without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves GraphQL schema metadata—type definitions, field information, documentation, and enum values. It performs introspection only, with no side effects, data modification, or execution capabilities. It is a pure Read operation used to understand API structure before making queries.
From the tool's definition Tool name 'get_graphql_schema_details' and description state it 'Returns full GraphQL type definitions' and 'get detailed field information'. The verb 'Returns' and 'get' indicate data retrieval with no modification capability.
Attacks that exploit this kind of access
Returns full GraphQL type definitions for the specified type names. Use this after get_graphql_schema to get detailed field information for types you need in your custom query. This tool provides the complete schema definition including: - All fields with their types and arguments - Field descriptions and documentation - Enum values - Interface implementations - Input object fields Example usage: - To understand App fields: typeNames: [. It is categorised as a Read tool in the Pointsyeah MCP Server, which means it retrieves data without modifying state.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for get_graphql_schema_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 Pointsyeah. Nothing to install.
get_graphql_schema_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 get_graphql_schema_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 get_graphql_schema_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.
get_graphql_schema_details is provided by the Pointsyeah MCP server (slack-workspace-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 →