get_user_member_profile
AI agents call get_user_member_profile to retrieve information from Clockify Time Tracking without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong signal of a read-only operation that retrieves user profile information. No modification, deletion, execution, or financial transaction is implied. Even with an empty description, the naming convention provides sufficient confidence that this is a data retrieval tool with minimal risk. Confidence is slightly reduced due to lack of explicit documentation.
From the tool's definition Tool name 'get_user_member_profile' indicates a retrieval operation with 'get' prefix. Description is empty and uninformative, but the name pattern strongly suggests querying profile data rather than modifying it.
Attacks that exploit this kind of access
get_user_member_profile. It is categorised as a Read tool in the Clockify Time Tracking MCP Server, which means it retrieves data without modifying state.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for get_user_member_profile: 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 Clockify Time Tracking. Nothing to install.
get_user_member_profile 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_member_profile 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_member_profile. 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_member_profile is provided by the Clockify Time Tracking MCP server (pypi:clockify-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 →