AI agents call structuredContent as a supporting operation in My workflows.
With no description provided, the tool's behavior cannot be determined from available information. The name 'structuredContent' suggests it may return or format structured data, which would be a Read/Other category, but without confirmation I default to Other with low confidence. The sibling tools suggest this is a demo/example MCP server, further reducing risk.
From the tool's definition Tool name is 'structuredContent' and description is empty/uninformative.
Attacks that exploit this kind of access
structuredContent. It is categorised as a Other tool in the My MCP Server, which means it performs auxiliary operations.
Register the My MCP server in PolicyLayer and add a rule for structuredContent: 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 My. Nothing to install.
structuredContent is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the structuredContent 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 structuredContent. 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.
structuredContent is provided by the My MCP server (kcbabo/everything-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 →