AI agents call get_user_attribute to retrieve information from AdButler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | User attribute ID |
user_db_id | number | Yes | User database ID |
Parameters from the server's own tool schema.
This tool retrieves information about a user attribute without creating, modifying, or deleting data. The verb 'Get' and the read-only nature of querying user attribute details place it in the Read category with low severity, as it poses minimal risk even if misused by an AI agent—it can only expose existing data, not alter or destroy it.
From the tool's definition Tool name 'get_user_attribute' and description 'Get details of a specific user attribute in a user database' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific user attribute in a user database. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_user_attribute accepts 2 parameters: id, user_db_id. Required: id, user_db_id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for get_user_attribute: 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 AdButler. Nothing to install.
get_user_attribute 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 get_user_attribute 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 get_user_attribute. 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.
get_user_attribute is provided by the AdButler MCP server (adbutler/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 →