custom_query_custom_objects
AI agents invoke custom_query_custom_objects to trigger actions in Marketo MCP Server. 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.
The name suggests a query/read operation against Marketo custom objects. However, 'custom_query' implies potentially arbitrary or flexible query execution, which could have side effects depending on implementation. With an empty description, confidence is low.
From the tool's definition Tool name 'custom_query_custom_objects' suggests querying custom objects, but description is empty and uninformative.
Attacks that exploit this kind of access
custom_query_custom_objects. It is categorised as a Execute tool in the Marketo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_query_custom_objects: 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 Marketo MCP Server. Nothing to install.
custom_query_custom_objects is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the custom_query_custom_objects 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 custom_query_custom_objects. 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.
custom_query_custom_objects is provided by the Marketo MCP Server MCP server (tyron-pretorius/marketo-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 →