my_function
AI agents call my_function as a supporting operation in Omada Identity MCP Server workflows.
The description is completely empty and the name 'my_function' is a generic placeholder that provides no meaningful signal about the tool's behavior or category. With no evidence to evaluate, confidence is very low and defaulting to Other is the only defensible choice. Severity is low by default given the lack of any information.
From the tool's definition Tool name is 'my_function' with an empty description, providing no information about what the tool does.
Attacks that exploit this kind of access
my_function. It is categorised as a Other tool in the Omada Identity MCP Server MCP Server, which means it performs auxiliary operations.
Register the Omada Identity MCP Server MCP server in PolicyLayer and add a rule for my_function: 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 Omada Identity MCP Server. Nothing to install.
my_function 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 my_function 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 my_function. 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.
my_function is provided by the Omada Identity MCP Server MCP server (omadaidentity/omada-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 →