Get controller log output.
AI agents call webots_get_logs to retrieve information from Webots MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical log output from a Webots robot controller. It performs a read-only query operation with no ability to modify state, execute commands, delete data, or trigger financial transactions. The worst-case misuse would be information disclosure of logs (low blast radius in a simulation context), making this a low-severity Read operation.
From the tool's definition Tool name 'webots_get_logs' with description 'Get controller log output' indicates retrieval of existing log data without modification or side effects.
Attacks that exploit this kind of access
Get controller log output. It is categorised as a Read tool in the Webots MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Webots MCP Server MCP server in PolicyLayer and add a rule for webots_get_logs: 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 Webots MCP Server. Nothing to install.
webots_get_logs 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 webots_get_logs 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 webots_get_logs. 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.
webots_get_logs is provided by the Webots MCP Server MCP server (luisfelipesena/webots-youbot-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 →