Get data from local system
AI agents call get_local_data to retrieve information from MCP Start App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves local system data without side effects. While the description is generic and doesn't specify *what* data is accessed, the name and context suggest query/fetch semantics. The main risk is information disclosure (low severity for local system metadata), mitigated by the fact that this is a local server with typical access controls.
From the tool's definition Tool name 'get_local_data' and description 'Get data from local system' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get data from local system. It is categorised as a Read tool in the MCP Start App MCP Server, which means it retrieves data without modifying state.
Register the MCP Start App MCP server in PolicyLayer and add a rule for get_local_data: 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 MCP Start App. Nothing to install.
get_local_data 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_local_data 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_local_data. 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_local_data is provided by the MCP Start App MCP server (nexus-aissam/mcp-local). 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 →