List all consents for a profile with optional filtering
AI agents call list_consents to retrieve information from Inoyu Apache Unomi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries consent data for a profile without creating, modifying, or deleting any data. Although it accesses sensitive personal data (consent preferences), the primary risk is unauthorized information disclosure rather than data mutation. Severity is medium because misuse could expose privacy-sensitive consent records, but it cannot directly harm data integrity or trigger external actions.
From the tool's definition Tool name 'list_consents' with description 'List all consents for a profile' indicates a retrieval operation with no side effects. The 'list' and 'get' operations on this server (get_consent, get_profile, get_my_profile, search_profiles) are read-only queries.
Documented attack patterns abuse exactly the kind of access list_consents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Inoyu Apache Unomi MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_consents:
{
"version": "1",
"default": "deny",
"tools": {
"list_consents": {}
}
}list_consents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all consents for a profile with optional filtering. It is categorised as a Read tool in the Inoyu Apache Unomi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Inoyu Apache Unomi MCP Server MCP server in PolicyLayer and add a rule for list_consents: 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 Inoyu Apache Unomi MCP Server. Nothing to install.
list_consents 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 list_consents 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 list_consents. 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.
list_consents is provided by the Inoyu Apache Unomi MCP Server MCP server (inoyu-dev/inoyu-mcp-unomi-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Inoyu Apache Unomi MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Inoyu Apache Unomi MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.