Low Risk

my_time

Lists the user's recorded hours for today (default) or a specific period. This tool automatically aggregates hours across ALL agencies the user belongs to, making it the preferred way to check total time today. Times are processed and displayed in Brasília time (BRT).

Part of the Clareo server.

my_time is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE CLAREO →

Free to start. No card required.

AI agents call my_time to retrieve information from Clareo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though my_time only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "my_time": {}
  }
}

See the full Clareo policy for all 45 tools.

Get this rule live on your own Clareo server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLAREO →

View all 45 tools →

These attack patterns abuse exactly the kind of access my_time gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so my_time only ever does what you allow.

SECURE CLAREO →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the my_time tool do? +

Lists the user's recorded hours for today (default) or a specific period. This tool automatically aggregates hours across ALL agencies the user belongs to, making it the preferred way to check total time today. Times are processed and displayed in Brasília time (BRT).. It is categorised as a Read tool in the Clareo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on my_time? +

Register the Clareo MCP server in PolicyLayer and add a rule for my_time: 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 Clareo. Nothing to install.

What risk level is my_time? +

my_time is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit my_time? +

Yes. Add a rate_limit block to the my_time 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.

How do I block my_time completely? +

Set action: deny in the PolicyLayer policy for my_time. 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.

What MCP server provides my_time? +

my_time is provided by the Clareo MCP server (@clareo/clareo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clareo tool call.

Deterministic rules across all 45 Clareo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.