query

${getQuerySafetyPreface(env)} Search the bundled and discovered OpenAPI specs by evaluating a JavaScript function. ${getOpenApiNote()} Available bindings (all zero-parameter — do NOT declare these as function parameters): \

Server Mc8yp schplitt/mc8yp
Category Execute
Risk class High
Parameters 00 required

What query does on Mc8yp

AI agents invoke query to trigger actions in Mc8yp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Why query needs a policy

The tool explicitly evaluates a JavaScript function at runtime. Regardless of the stated intent (searching OpenAPI specs), arbitrary JavaScript evaluation is an Execute-category action. The blast radius is high because an AI agent could craft malicious JavaScript, and this sits within a full Cumulocity API surface server that also has an 'execute' sibling tool, amplifying potential misuse.

From the tool's definition 'Search the bundled and discovered OpenAPI specs by evaluating a JavaScript function' — the tool executes a JavaScript function to perform its operation.

Questions about query

What does the query tool do? +

${getQuerySafetyPreface(env)} Search the bundled and discovered OpenAPI specs by evaluating a JavaScript function. ${getOpenApiNote()} Available bindings (all zero-parameter — do NOT declare these as function parameters): \. It is categorised as a Execute tool in the Mc8yp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query? +

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

What risk level is query? +

query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit query? +

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

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

query is provided by the Mc8yp MCP server (schplitt/mc8yp). 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.