Get the robot settings
AI agents call get_robot_settings to retrieve information from Mycobot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration or state information from the myCobot robot. It performs a read-only query without creating, modifying, executing code, deleting data, or committing financial transactions. The low severity reflects minimal blast radius—accessing robot settings poses no immediate operational risk.
From the tool's definition Tool name 'get_robot_settings' and description 'Get the robot settings' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_robot_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mycobot, and nothing reaches the server without passing your rules. This is the rule we recommend for get_robot_settings:
{
"version": "1",
"default": "deny",
"tools": {
"get_robot_settings": {}
}
}get_robot_settings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the robot settings. It is categorised as a Read tool in the Mycobot MCP Server, which means it retrieves data without modifying state.
Register the Mycobot MCP server in PolicyLayer and add a rule for get_robot_settings: 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 Mycobot. Nothing to install.
get_robot_settings 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_robot_settings 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_robot_settings. 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_robot_settings is provided by the Mycobot MCP server (neka-nat/mycobot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mycobot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Mycobot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.