AI agents call get_apps_and_websites to retrieve information from Rize without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves usage statistics about applications and websites within a specified time period. It performs no modification, deletion, execution, or financial operation. The action is purely informational and has no side effects on the system or data state. Low severity reflects minimal risk even if misused by an AI agent—the worst outcome would be unauthorized viewing of productivity analytics.
From the tool's definition Tool name 'get_apps_and_websites' and description 'Get apps and websites usage within a time range' indicate data retrieval only. The verb 'Get' and the query-like nature (retrieving historical usage data) align with read-only operations.
Attacks that exploit this kind of access
Get apps and websites usage within a time range. It is categorised as a Read tool in the Rize MCP Server, which means it retrieves data without modifying state.
Register the Rize MCP server in PolicyLayer and add a rule for get_apps_and_websites: 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 Rize. Nothing to install.
get_apps_and_websites 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_apps_and_websites 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_apps_and_websites. 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_apps_and_websites is provided by the Rize MCP server (rize-io/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 →