ソラカメのイベント詳細を取得します
AI agents call get_soracam_event to retrieve information from SORACOM Data Reader MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves event details from SoraCam (SORACOM's camera service). The 'get' prefix and the description indicating data retrieval classify it as a Read operation. There is no indication of data modification, deletion, code execution, or financial impact. The severity is low because reading camera event metadata poses minimal risk—the data retrieved already exists and cannot be altered by the query itself.
From the tool's definition Tool name 'get_soracam_event' and description 'ソラカメのイベント詳細を取得します' (retrieves SoraCam event details) indicate a retrieval operation.
Attacks that exploit this kind of access
ソラカメのイベント詳細を取得します. It is categorised as a Read tool in the SORACOM Data Reader MCP MCP Server, which means it retrieves data without modifying state.
Register the SORACOM Data Reader MCP server in PolicyLayer and add a rule for get_soracam_event: 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 SORACOM Data Reader MCP. Nothing to install.
get_soracam_event 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_soracam_event 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_soracam_event. 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_soracam_event is provided by the SORACOM Data Reader MCP server (leaveanest/alt-soracom-data-reader-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 →