aasagenticawesomeskills__export_selection_evidence

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Medium RISK CLASS

Category Write

Parameters 44 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/aasagenticawesomeskills--export-selection-evidence.md

WHAT IT DOES

What aasagenticawesomeskills__export_selection_evidence does on Rokha

AI agents use aasagenticawesomeskills__export_selection_evidence to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.

Parameter	Type	Required
`project`	object	Yes
`dimensions`	array	Yes
`capabilities`	array	Yes
`manifestDigest`	string	Yes

Parameters from the server's own tool schema.

RISK

Why aasagenticawesomeskills__export_selection_evidence is rated Medium

Creates a new JSON sidecar file from session data; reversible write operation with audit trail.

From the tool's definition Build a canonical, read-only aas-selection-evidence.json sidecar from trace

Risk signalsAccepts file system path (capabilities[].evidence[].path) · High parameter count (21 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs aasagenticawesomeskills__export_selection_evidence safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aasagenticawesomeskills__export_selection_evidence, this is the rule to start with:

aasagenticawesomeskills__export_selection_evidence Rate-limited

aasagenticawesomeskills__export_selection_evidence stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aasagenticawesomeskills__export_selection_evidence": {
      "limits": [
        {
          "counter": "aasagenticawesomeskills__export_selection_evidence_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every aasagenticawesomeskills__export_selection_evidence call is checked against it from then on.

FAQ

Questions about aasagenticawesomeskills__export_selection_evidence

What does the aasagenticawesomeskills__export_selection_evidence tool do? +

Build a canonical, read-only aas-selection-evidence.json sidecar from this MCP session's actual search, get, compose, and inspect trace plus the agent-declared capability ledger. Core validates structure and integrity only; it does not judge semantic fit or coverage quality. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does aasagenticawesomeskills__export_selection_evidence accept? +

aasagenticawesomeskills__export_selection_evidence accepts 4 parameters: project, dimensions, capabilities, manifestDigest. Required: project, dimensions, capabilities, manifestDigest. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on aasagenticawesomeskills__export_selection_evidence? +

Register the Rokha MCP server in PolicyLayer and add a rule for aasagenticawesomeskills__export_selection_evidence: 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 Rokha. Nothing to install.

What risk level is aasagenticawesomeskills__export_selection_evidence? +

aasagenticawesomeskills__export_selection_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit aasagenticawesomeskills__export_selection_evidence? +

Yes. Add a rate_limit block to the aasagenticawesomeskills__export_selection_evidence 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.

How do I block aasagenticawesomeskills__export_selection_evidence completely? +

Set action: deny in the PolicyLayer policy for aasagenticawesomeskills__export_selection_evidence. 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.

What MCP server provides aasagenticawesomeskills__export_selection_evidence? +

aasagenticawesomeskills__export_selection_evidence is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →